From: Jan Kara <jack@suse.cz>
To: Pavel Machek <pavel@ucw.cz>
Cc: Theodore Ts'o <tytso@mit.edu>,
kernel list <linux-kernel@vger.kernel.org>,
jack@suse.cz, linux-ext4@vger.kernel.org,
adilger.kernel@dilger.ca, Dmitry Monakhov <dmonakhov@openvz.org>
Subject: Re: ext4: 3.17? problems
Date: Wed, 1 Oct 2014 10:48:10 +0200 [thread overview]
Message-ID: <20141001084810.GA17405@quack.suse.cz> (raw)
In-Reply-To: <20140930210108.GB14283@amd>
On Tue 30-09-14 23:01:08, Pavel Machek wrote:
> > > On next boot to Debian stable, I got stacktrace, and messages about
> > > ext4 corruption. Back to Debian testing. systemd ran fsck, determined
> > It would be really good to get those messages... Ideally you could also
> > use
> > e2image -r <partition> | bzip2 -c
> > to store fs metadata before doing anything else with the fs to a usb stick.
> > That is invaluable for future analysis.
>
> Too late for that :-(.
OK, you can take a note for next time ;)
> > > it can't fix it, dropped me into emergency shell, _but mounted the
> > > filesstem, anyway_. Oops.
> > What kernel versions are you running in Debian testing and stable?
>
> Debian testing was 3.17-rc4, AFAICT. For debian stable -- not sure.
OK, there were some changes to orphan list locking in 3.17-rc1. If I
screwed up it could cause orphan list corruption. But for now I don't think
that's the issue.
> > My guess would be that kernel had problems only during orphan inode
> > recovery (i.e. when deleting already deleted files) and we let the mount
> > proceed if this fails because it's a relatively harmless problem.
>
> Is there some phase during shutdown where journalling no longer
> protects fs integrity?
No. We first finish all modifications to the fs and only after that clean
up the journal. So that makes all changes to the fs protected.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2014-10-01 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 10:44 ext4: 3.17? problems Pavel Machek
2014-09-28 12:46 ` Theodore Ts'o
2014-09-30 21:01 ` Pavel Machek
2014-09-30 23:18 ` Henrique de Moraes Holschuh
2014-10-01 8:50 ` Jan Kara
2014-10-01 8:48 ` Jan Kara [this message]
2014-09-29 9:36 ` Dmitry Monakhov
2014-09-29 11:44 ` Jan Kara
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=20141001084810.GA17405@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).