On Fri, Jul 3, 2009 at 7:38 AM, Andreas Dilger<adilger@xxxxxxx> wrote: >> - Immediately running e2fsck on the volume before ever mounting it >> will not complete, and results in the following: >> # e2fsck -n /dev/md2 >> e2fsck 1.41.7 (29-June-2009) >> Error reading block 2435874816 (Attempt to read block from filesystem >> resulted in short read). Ignore error? no >> /dev/md2: Attempt to read block from filesystem resulted in short read >> while reading block 2435874816 >> /dev/md2: Attempt to read block from filesystem resulted in short read >> reading journal superblock >> e2fsck: Attempt to read block from filesystem resulted in short read >> while checking ext3 journal for /dev/md2 > > It looks like there may be some problem with the underlying device? > I posted a program here a few months ago called "ll_ver_dev" which > can quickly (or slowly) verify that writes and reads to different > offsets in a block device return consistent data. The quick version > will detect such problems as 32-bit overflows, but if you are having > strange problems you might need to run the full version. > > You could also try running with a filesystem just under 16TB and > verifying that works. > Running with a filesystem just under 16TB works fine. Forgive my ignorance, but for the life of me I couldn't find an reference anywhere about your "ll_ver_dev" program. But doing dd if=/dev/zero across the entire ~18TB didn't report any errors, so I believe the underlying device is in good shape. Running e2fsck with an external journal did change the behavior though. Basically it no longer chokes on the journal, but it does somewhere else: e2fsck 1.41.8 (11-July-2009) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Error reading block 576192512 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore error? no e2fsck: Can't read an block bitmap while retrying to read bitmaps for /dev/md2 e2fsck: aborted >> - Mounting with -o noload does appear to work, and reading and >> writing seems to work fine. > > That's because the journal is not being used, which is what seems to > be having the problem. I wonder if the journal is beyond 8TB or > beyond 16TB for some reason and this is causing grief? > Perhaps, but I'm not sure. Using an external journal device also worked the same as not loading the journal. -Justin -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
