From: Eric Sandeen <sandeen@redhat.com>
To: fabian-buettner@gmx.de
Cc: linux-ext4@vger.kernel.org
Subject: Re: Corrupt superblocks
Date: Wed, 04 Nov 2009 16:24:04 -0600 [thread overview]
Message-ID: <4AF1FF04.9040503@redhat.com> (raw)
In-Reply-To: <200911042307.40776.fabian-buettner@gmx.de>
fabian-buettner@gmx.de wrote:
> So maybe i did harm my fs by running e2fsck -b?
If /dev/vg/root didn't exist, no filesystem was harmed in the process I
am sure. :)
> Because running fsck afterwards gave me a lot of those Group descriptor
> checksum fixing proposals?
> I am surprised that e2fsck just told me that my fs is clean.
>
> Do you have a clue why an entry in my /etc/fsab like
> /dev/vg/root / ext4 noatime 0 0
This tells the initscripts not to try running fsck on /dev/vg/root at
all (see man fstab)
> works, while
> /dev/vg/root / ext4 noatime 0 1
> doesnt?
These are probably questions for your distribution; it sounds like the
initscripts are not able to point e2fsck at the proper device, at the
proper time...
-Eric
> - fabian
next prev parent reply other threads:[~2009-11-04 22:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 18:39 Corrupt superblocks fabian-buettner
2009-11-04 19:21 ` Eric Sandeen
2009-11-04 20:40 ` [PATCH] make unified logs on ext2 Alexey Fisher
2009-11-05 4:50 ` Andreas Dilger
2009-11-05 7:33 ` [PATCH] Unify log messages in ext2 Alexey Fisher
2009-11-06 14:53 ` Alexey Fisher
2009-11-17 21:23 ` Jan Kara
2009-11-18 19:26 ` Alexey Fisher
2009-11-19 11:17 ` [PATCH v2] " Alexey Fisher
2009-11-19 11:22 ` Alexey Fisher
2009-11-19 11:30 ` [PATCH v3] " Alexey Fisher
2009-11-19 14:32 ` Jan Kara
2009-11-19 18:12 ` [PATCH v4] " Alexey Fisher
2009-11-20 9:56 ` Jan Kara
2009-11-21 10:27 ` Alexey Fisher
2009-11-04 21:56 ` Corrupt superblocks fabian-buettner
2009-11-04 21:59 ` Eric Sandeen
2009-11-04 22:07 ` fabian-buettner
2009-11-04 22:24 ` Eric Sandeen [this message]
2009-11-09 20:18 ` fabian-buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF1FF04.9040503@redhat.com \
--to=sandeen@redhat.com \
--cc=fabian-buettner@gmx.de \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.