Re: nilfs2 fails to mount after io/error

From: Chris Samuel <chris-Ru3vu9m2XlBAfugRpC6u6w@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: nilfs2 fails to mount after io/error
Date: Thu, 4 Dec 2008 19:30:59 +1100	[thread overview]
Message-ID: <200812041931.02528.chris@csamuel.org> (raw)
In-Reply-To: <20081204.170654.88475919.ryusuke-sG5X7nlA6pw@public.gmane.org>

[-- Attachment #1.1: Type: text/plain, Size: 729 bytes --]

On Thu, 4 Dec 2008 7:06:54 pm Ryusuke Konishi wrote:

> This never occurs if the block device is
> supporting 'write barrier' feature properly.
>
> Could you tell me the kernel version that you are using?
>
> I feel that an additional disk flush operation may be
> needed for older kernels or such devices. (Of course,
> first priority should be on making fsck.)

It's worth remembering that (unless something has changed recently) filesystems 
on a logical volume using LVM won't have barriers either.

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

[-- Attachment #2: Type: text/plain, Size: 158 bytes --]

_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users