linux-kernel - Re: POHMELFS high performance network filesystem release.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080425210315.GA3712@2ka.mipt.ru>
Date:	Sat, 26 Apr 2008 01:03:15 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: POHMELFS high performance network filesystem release.

Hi.

On Fri, Apr 25, 2008 at 07:25:50PM +0200, Andi Kleen (andi@...stfloor.org) wrote:
> Evgeniy Polyakov <johnpol@....mipt.ru> writes:
> 
> > It is work-in-progress, and network protocol is not stable yet.
> 
> Congratulations. I'm sure it was a lot of work.

Well, not _that_ lot of work, but it is interesting, so...
It was at least once time rewriten mostly from scratch to allow all those
shiny things. It is not in-advance design, but kind of evolution based
on my filesystem studying.

> But could you please quickly expand how useful it is at this state? Is
> it already far enough that someone could save some data on it and use
> it without it crashing all the time?
> 
> It's unclear even from your status report.

Well, it does not crash in iozone, huge untar, kernel compilations
and big file copies. And it works reliably enough to make md5 sums be
equal on both server and clients, but I will not be surprised if it
contains some bugs. I also will not be surprised, if current server 
behaviour does not match POSIX expectations (I'm curios of NFS
matches that), but at least this behaviour will be much more clean
with transaction introduction and server support for them.

So, it works for usual NFS-like workload, but since it is rather young
FS (this particular design implementation exists for about couple of
months), there may be some questions...

Getting that POHMELFS is really simple and its design is oriented to be
as open as possible without burden of old age problems and
compatibilities, it is not a any kind of a problem to locate and fix a
bug, so I'm very open for any kind of reports.

-- 
	Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/