On Wed, Nov 08, 2006 at 04:06:23PM -0700, Andreas Dilger wrote:
I would suggest that even while this is not supported, it would be prudent
to fix such a bug. It might be possible to hit a similar problem if there
is corruption of the on-disk data in the journal and oopsing the kernel
isn't a
On Wed, Nov 08, 2006 at 11:22:15AM -0800, Suzuki wrote:
I exported a disk partition using nbd protocol. On the nbd client, I
make reiserfs and run fsstress test case on this partition. At the same
time, I mount this partition on the nbd server. Then Oops appears as
following:
ReiserFS:
On Fri, Sep 16, 2005 at 12:39:48PM -0700, Hans Reiser wrote:
Most of my customers remark that Namesys code is head and shoulders
above the rest of the kernel code. So yes, it is different. In
particular, they cite the XFS code as being so incredibly hard to read
that its unreadability is
On Fri, Sep 16, 2005 at 04:50:45PM -0400, Lennart Sorensen wrote:
Well my experience with XFS for about 6 months using 2.6 kernels has
been about as good as my experience with reiserfs 3.6 back when 2.4
was fairly new.
That's why I run ext3.
I don't need my filesystem locking up, leaking
