From: Theodore Ts'o <tytso@mit.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
jack@suse.cz, linux-ext4@vger.kernel.org,
adilger.kernel@dilger.ca
Subject: Re: ext4: 3.17? problems
Date: Sun, 28 Sep 2014 08:46:58 -0400 [thread overview]
Message-ID: <20140928124658.GB6694@thunk.org> (raw)
In-Reply-To: <20140928104456.GA17400@amd>
On Sun, Sep 28, 2014 at 12:44:56PM +0200, Pavel Machek wrote:
>
> After update to debian testing, my machine sometimes fails to
> reboot. (aptitude upgrade seems to be the trigger).
>
> So I had to hard power-down the machine. That should be perfectly
> safe, as ext4 has a journal, and this is plain SATA disk, right?
>
> On next boot to Debian stable, I got stacktrace, and messages about
> ext4 corruption. Back to Debian testing. systemd ran fsck, determined
> it can't fix it, dropped me into emergency shell, _but mounted the
> filesstem, anyway_. Oops.
I've been running 3.17-rc4 plus the ext4 dev patches and due to either
regressions in i915 or the X server (not sure which) over the last
couple of weeks, I've had to power-down my system a number of times
after the system has hung when either shutting down the X server or
when trying to add or remove an external display. So I've had to
unfortunately do a fair number of hard-power-offs on my T540p, and
I've not noticed any like what you've described.
Can you give any more details? Are you using LVM or dm-crypt? Is
this repeatable?
Cheers,
- Ted
next prev parent reply other threads:[~2014-09-28 12:46 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 [this message]
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
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=20140928124658.GB6694@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.