Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64

From	Sarah Newman <srn@prgmr.com>
Newsgroups	linux.debian.bugs.rc
Subject	Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64
Date	2020-07-16 06:00 +0200
Message-ID	<At3dT-1RX-1@gated-at.bofh.it> (permalink)
References	<Aq6hX-80m-1@gated-at.bofh.it> <Aq8MO-1eA-3@gated-at.bofh.it> <Aq6hX-80m-1@gated-at.bofh.it> <Aq8MO-1eA-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 7/7/20 8:13 PM, Ben Hutchings wrote:
> Control: reassign -1 src:linux
> Control: tag -1 moreinfo
> 
> On Tue, 2020-07-07 at 17:30 -0700, Sarah Newman wrote:
>> Package: linux-signed-amd64
>> Version: 4.19.0-9-amd64
>>
>> We've had two separate reports now of debian buster users running
>> 4.19.0-9-amd64 who experienced serious file system corruption.
> 
> Which version?  (I.e. what does "uname -v" or
> "dpkg -s linux-image-4.19.0-9-amd64" say?)
> 
>> - Both were using ext3
>> - Both are running Xen HVM, but I do not have reason to believe this to be related


I doubt it matters, but the two observed failures were on hosts with Xeon v2's (we're currently working on fixing that.)

New reports:

* Buster 4.19.0-6-amd64, ext3, uptime ~36 weeks, Xeon v4, no failure
* Buster 4.19.0-9-amd64, ext4, uptime ~6 days, Xeon v2, no failure (but it hasn't even been a week)
* Arch Linux v5.6.11, ext3, uptime ~9 weeks, Xeon v2, no failure

--Sarah

Back to linux.debian.bugs.rc | Previous | Next | Find similar | Unroll thread

Thread

Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64 Sarah Newman <srn@prgmr.com> - 2020-07-16 06:00 +0200

csiph-web