From: Theodore Ts'o <tytso@mit.edu>
To: Barry Kauler <bkauler@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: f.s. corruption ext3, kernel 4.4.8
Date: Sun, 24 Apr 2016 22:14:13 -0400 [thread overview]
Message-ID: <20160425021413.GM20980@thunk.org> (raw)
In-Reply-To: <CABWT5yh98_f5=Y0k7_ELHM=fn35s0Eb5D5kmDCSsFMikgmscnQ@mail.gmail.com>
On Mon, Apr 25, 2016 at 09:46:19AM +0800, Barry Kauler wrote:
> I sent this direct to Greg KH yesterday morning. 24 hours later got an
> automated reply to send my email to one of the lists.
>
> I'm a user, not a kernel developer, gotta post this somewhere.
>
> I reckon this is urgent.
> I have rolled back from 4.4.8 to 4.4.7, have used heavily for 24 hours
> since then,
> no problem. So, it's the kernel, not my laptop.
No one else has reported any problems to date, and there are only two
changes in ext4 code between v4.4.7 and v4.4.8, neither of which seem
at all likely to cause file system corruption.
ee8516a ext4: ignore quota mount options if the quota feature is enabled
321299a ext4: add lockdep annotations for i_data_sem
If you can send us the "EXT4-fs error" message that would have been
logged before the file system went read-only, or the output from
e2fsck, that might be helpful in matching up your report from any
others, or to have some insight into what might have happened.
Unfortunately, without any more information there's not much we can do
with your report other than to keep an ear out in case anyone else
complains.
Thanks,
- Ted
next prev parent reply other threads:[~2016-04-25 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 1:46 f.s. corruption ext3, kernel 4.4.8 Barry Kauler
2016-04-25 2:14 ` Theodore Ts'o [this message]
2016-04-25 2:33 ` Barry Kauler
2016-04-25 16:51 ` Eric Sandeen
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=20160425021413.GM20980@thunk.org \
--to=tytso@mit.edu \
--cc=bkauler@gmail.com \
--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 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).