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
** Description changed:
- Writing data to a 3 TB ext4-formatted logical volume on a 2x6 TB mdadm
- raid 1 mirror always results in a GPF within 1 minute of writing the
- data. Disks seem to be OK smart-wise.
+ mkfs.ext3 always causes a kernel panic on both of my WD 6 TB drives
+ while writing the
More detailed SMART info:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051Pre-fail Always
- 0
3 Spin_Up_Time0x0027 241 201 021Pre-fail Always
-
Additional info:
A GPF also occurs when creating the filesystem on the LV using mkfs.ext3, while
creating the inode tables.
Since mkfs.ext4 doesn't do this, it happens later when more data is being
written to the lv.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
- Writing data to a 3 TB ext4-formatted logical volume on a 2x6 TB mdadm
- raid 1 mirror always results in a GPF within 1 minute of writing the
- data. Disks seem to be OK smart-wise.
-
- When the GPF occurs, the md1 raid volume gets degrated, the entire
+ Writing lots of
