If you can see the GPF happen when mkfs.ext3 is writing to a bare
block device (/dev/sdc1 or /dev/sdd1), then it's not involving the
file system code at all, but just the block device or device driver
code. It's clearly not a file system bug at all, nor is it a
e2fsprogs bug, because nothing from user space should be able to
trigger this kind of failure --- nor have we seen anyone report
anything even vaguely like this on upstream kernels.
So it's likely that this is either triggered by some hardware bug, a
device-driver specific bug if you are using something esoteric, or a
some other miscellaneous bug introduced in the Ubuntu kernel.
It's likely that the bug is corrupting the data structures which track
the page cache buffers, judging from the stack trace and the fact that
the process which died was something entirely unrelated to the the
mkfs.ext3:
> - Nov 16 09:26:03 nas kernel: [ 230.610810] CPU: 1 PID: 1927 Comm:
vsftpd Tainted: G D 3.13.0-39-generic #66-Ubuntu
It might be useful to try running mkfs.ext3 to a USB-attached storage
device, and see if that triggers the problem. If doesn't and you can
safely write to the USB drive, then the figure of suspicion would
pretty squarely fall on the hardware device or its device driver (or
the Ubuntu kernel, of course).
It might also be useful to try this on another server altogether, or
to try swapping out to another kernel (say, an upstream kernel).
Cheers,
- Ted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393151
Title:
mkfs.ext3 causes kernel panic on new WD 6 TB drive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1393151/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
