I would "dd" to a file and use loopback to see what's on it. -- William On Mon, Jul 20, 2015 at 08:43:42AM -0400, Mike Kallies wrote:
Hey Everyone,
This might be worth a good laugh.
tl;dr version: filesystem is about 100 blocks too big for the device, not sure why.
- mount says fs is too big for device - fsck says fs is too big for device - resize2fs says to fsck - fsck says it's ok - resize2fs says to fsck
I can see the contents under testdisk. It's nothing which isn't backed up elsewhere.
It's a 1.5TB filesystem, so it can be slow to work with. The plan was to check what I put on it and repurpose the disk. At this point I'm thinking I'll use testdisk to poke around then repartition and reformat.
Any thoughts about this?
Mike
==
[4312277.804064] EXT4-fs (sdd3): mounting ext3 file system using the ext4 subsystem [4312277.804263] EXT4-fs (sdd3): bad geometry: block count 375655936 exceeds size of device (375655832 blocks) [root@local ~]# resize2fs /dev/sdd3 resize2fs 1.42.9 (28-Dec-2013) Please run 'e2fsck -f /dev/sdd3' first.
[root@local ~]# e2fsck -f /dev/sdd3 e2fsck 1.42.9 (28-Dec-2013) The filesystem size (according to the superblock) is 375655936 blocks The physical size of the device is 375655832 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no 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 /dev/sdd3: 99751/93921280 files (3.9% non-contiguous), 348286205/375655936 blocks [root@local ~]# resize2fs /dev/sdd3 resize2fs 1.42.9 (28-Dec-2013) Resizing the filesystem on /dev/sdd3 to 375655832 (4k) blocks. resize2fs: Attempt to read block from filesystem resulted in short read while trying to resize /dev/sdd3 Please run 'e2fsck -fy /dev/sdd3' to fix the filesystem after the aborted resize operation. [root@local ~]# --- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk