Zbr's days.
←July→
Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    
←2008→
Months
Jan Feb Mar
Apr May Jun
JulAug Sep
Oct Nov Dec

About TODO Blog RSS Old blog Projects Gallery Notes

Mon, 07 Jul 2008

New POHMELFS release.

Irish 'Clontarf' and Scotch 'Grant's' helped to rule this release out.

This POHMELFS release features include:

  • Strong cryptography support. One can encrypt whole data channel (except headers) and/or hash/digest it. System will try to autoconfigure itself and if server does not support requested algorithms, mount will either fail (if special mount option is specified) or disable appropriate algorithm usage.
  • Bug fixes.
Cryptography support is essential addition to the POHMELFS core. It was implemented with performance in mind, so that processing speeds would not drop noticeble even in case of very CPU-hungry operations (one can check performance graphs).
POHMELFS utilizes pool of crypto threads (its number can be specified via mount option), which perform data crypto processing and submit it either to network or VFS layer.

Now I will concentrate mostly on userspace server features, mainly its distributed facilities, current ability to write data to multiple servers and balance reading among them is not enough for POHMELFS, but it will be an essential building block of the fully distributed fault-tolerant paralllel filesystem.

If this development will require some changes in kernel side (namely network protocol extension), it will be don in the upcoming releases with possible found bug fixes.

As usual, you can grab sources from archive or via GIT tree.
You can also check POHMELFS homepage to get more details on its design and supported features.

P.S. I think I will have some rest out of this project for several days, which will allow me to concentrate on main POHMELFS features and work out rough edges. I will switch to DST and netchannels (main to make a new releases) and then will devote some time to captcha cracking algorithms.

/devel/fs :: Link / Comments (4)

anonymous wrote at 2008-07-12 04:32:

"I will switch to DST and netchannels (main to make a new releases) and then will devote some time to captcha cracking algorithms. " --> so what's up with DST ? or do you alter the order ? or decided not to switch to DST ? :)

Thanks a lot!

Zbr wrote at 2008-07-12 10:25:

I remember, right now I'm just having bits of rest, and I can not have a rest without doing anything, so there are some another tasks :)

benpi wrote at 2008-07-13 13:23:

Hi, POHMELFS is already very impressive, thank you for this work! I can't help but dream about Linux' future with things like "POHMELFS over brtfs" (aka "zfs? no, thanks")... :)

You alway write "the client" (singular) and "the servers" (plural). Is POHMELFS intended to handle several simultaneous clients (ie. provide locking mechanisms and so), so we could throw away NFS for real? (because, that's now the only remaining cause of NFS use, we already have good alternatives for the "only one client" case, like soft raid over AoE, iSCSI, or drbd)?

The project's homepage says "POHMELFS protocol was proven to be superior to NFS in lots (if not all, then it is in a roadmap) operations" so I have good hopes ;).

Zbr wrote at 2008-07-14 00:14:

POHMELFS server can handle multiple clients, but there is no locking between them, instead there is a cache coherency mechanism, which provides different sematics for the users. I will introduce special locking to be POSIX-compliant, but I will design them with distributed facilities in mind, so it is not implemented yet.

Please solve this captcha to be allowed to post (need to reload in a minute): 98 * 63

Name:
URL (optional):
Captcha:
Comments: