It's happened again. I've spent several hours on this and I've been able
to recreate the failure under some synthetic conditions with a
sacrificial VM.
The filebench defaults do not cause an ext4 crash for me, but the
following do:
load workloads/fileserver
set $dir=/tmp/
set $nfiles=20
set
I'm posting again to add that I conducted some more tests and ext3 does
not encounter corruption under the same conditions. I hope this
information is helpful to others, if anyone needs more information let
me know and I'll see what I can do. I'll probably switch my own VMs to
ext3 so I don't have
chris,
Here is what you asked for, sorry for not getting it earlier.
I don't use virsh. This is how I started KVM to trigger the problem
interactively (curses interface):
kvm -drive
file=/dev/raid/shared,media=disk,if=none,cache=none,aio=native,format=raw,id=hd0
-device virtio-blk-pci,drive=hd0
Oops...the above kvm command line is correct but it did not crash with -m 1000,
that's what production is using now.
It was crashing consistently with -m 512 about a minute into the synthetic FS
load.
--
You received this bug notification because you are a member of Kernel
Packages, which is
It happened here again.
8/24 ext4 corruption
9/14 ext4 corruption
9/29 update/reboot
10/16 ext4 corruption
This time the corruption was severe. 1743 files from multiple directories got
moved into lost+found.
It took me almost 2 hours this morning to verify & fix everything. Fortunately
every
I'm on Debian, but it's happening to me as well.
KVM with virtual disks backed by LVM volumes on the host.
Both the VM and the host are running
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u2 (2015-07-17)
I have a "PE 2950III Intel(R) Xeon(R) CPU X5460 @ 3.16GHz" server here
and I've been trying to test this out. I'm using an "rsync" copy of an
original server exhibiting the problem. So far though I've been unable
to reproduce the original error at all.
It would seem that using the exact same
Good work.
We also have PE2950III systems running "Intel(R) Xeon(R) CPU X5460 @
3.16GHz".
If this is indeed the fix, I'm confused why it would only affect certain cpus?
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=7dec5603b6b8dc4c3e1c65d318bd2a5a8c62a424
I'll have
I'd like to follow up because the issue seems to have cleared up for us
after installing linux 5.0.1 about 40 days ago. It's hard to say whether
everyone is experiencing the same bugs, but give 5.x a shot and let us
know how it goes!
Just to recap. Every week or so we were seeing R/O file
9 matches
Mail list logo
