Your message dated Fri, 30 Sep 2011 18:26:59 -0400
with message-id <[email protected]>
and subject line Re: Bug#639894: e2fsprogs: don't allow -D when fsck'ing a
read-only mounted fs
has caused the Debian Bug report #639894,
regarding e2fsprogs: don't allow -D when fsck'ing a read-only mounted fs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
639894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639894
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.42~WIP-2011-07-02-1
Severity: normal
Hi.
Whenever I check a read-only mounted ext filesystem with -D -f (I guess the -f
shouldn't matter, though)
I get some worrying kernel errors on the filesystem, as soon as I remount,rw it
again and e.g.
reboot the system then (typically when fsck'ing the root-fs).
Not sure whether this is actually serious or not, but perhaps considering to
dissallow or ignore
-D on ro-mountes fs could be worth it.
Cheers,
Chris.
--- End Message ---
--- Begin Message ---
tags 639894 +wontfix
thanks
On Wed, Aug 31, 2011 at 02:15:12PM +0200, Christoph Anton Mitterer wrote:
>
> Whenever I check a read-only mounted ext filesystem with -D -f (I
> guess the -f shouldn't matter, though) I get some worrying kernel
> errors on the filesystem, as soon as I remount,rw it again and e.g.
> reboot the system then (typically when fsck'ing the root-fs).
>
> Not sure whether this is actually serious or not, but perhaps
> considering to dissallow or ignore -D on ro-mountes fs could be
> worth it.
I could prohibit this, but then it becomes impossible to use -D on a
read-only mounted root file system, which some system administrators
might want to do without using a rescue CD.
Your mistake was remounting the file system read-write. In general,
if the e2fsck has made *any* change to the file system, either when it
is fixing a file system corruption, or because of the request to
optimize directories using the -D option, you must not remount the
file system read-write. Instead, you must reboot the system, after
e2fsck completes.
If I disallowed this, it would make e2fsck "safer", but then it would
mean that you wouldn't be able to use -D on a root file system at all
without rebooting into a rescue CD-ROM image. And that would be sad,
because there is a safe way to do this.
And indeed, e2fsck should have told you:
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: ***** REBOOT LINUX *****
So I've already put in as much warning as I can, short of assuming
that system administrators are idiots, and preventing them from doing
something useful just in case they ignore a very strongly worded
admonition after e2fsck completes. And it's not the Linux way to
assume that users are idiots.
- Ted
--- End Message ---
