[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170524215622.fh7yin4fttggw36f@thunk.org>
Date: Wed, 24 May 2017 17:56:22 -0400
From: Theodore Ts'o <tytso@....edu>
To: Konstantin Chistyakov <Konstantin.Chistyakov@...agon-software.com>
Cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: libext2fs: don't flush to device opened in read-only mode
On Mon, May 22, 2017 at 09:48:00AM +0000, Konstantin Chistyakov wrote:
> From: Konstantin Chistyakov <Konstantin.Chistyakov@...agon-software.com>
> Date: Tue, 19 May 2017 09:23:29 -0600
> Subject: [PATCH] libext2fs: don't flush to device opened in read-only mode
>
> From: Konstantin Chistyakov <Konstantin.Chistyakov@...agon-software.com>
>
> If the e2fsck is called with both -f -n options, the checking completing with a flushing error (retcode 8).
>
> Catch error from the unix_flush() fsync(data->dev) when data->dev is opened in read-only mode:
I can't reproduce this problem. What storage device or operating
system are you using?
That being said, this is probably the wrong place to fix it. The
better fix is in e2fsck/unix.c, by adding a read-only test.
- Ted
Powered by blists - more mailing lists