Date: Fri, 20 Feb 2004 22:25:57 +1100 (EST) From: Tim Robbins <tim@robbins.dropbear.id.au> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/63118: e2fsprogs thinks devices are zero bytes in size Message-ID: <20040220112557.7B02541AF@robbins.dropbear.id.au> Resent-Message-ID: <200402201130.i1KBUCqu095450@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 63118
>Category: ports
>Synopsis: e2fsprogs thinks devices are zero bytes in size
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Feb 20 03:30:12 PST 2004
>Closed-Date:
>Last-Modified:
>Originator: Tim Robbins
>Release: FreeBSD 5.2-tjr i386
>Organization:
The FreeBSD Project
>Environment:
System: FreeBSD cat.robbins.dropbear.id.au 5.2-tjr FreeBSD 5.2-tjr #1: Fri Jan 23 02:11:08 EST 2004 tim@cat.robbins.dropbear.id.au:/usr/obj/home/tim/p4/src/sys/CAT i386
>Description:
Many of the utilities in e2fsprogs seem to think that devices are zero
bytes in size, and complain that a specified disk device is
"not a block special device". FreeBSD does not support block special devices.
e2fsck does not seem to work at all. It complains about a "short read"
on filesystems that mount fine with mount_ext2fs and do not have any
problems when checked with e2fsck running on Debian 3.0 or my modified
version of NetBSD's fsck_ext2fs
>How-To-Repeat:
# mke2fs /dev/ad1s1
mke2fs 1.32 (09-Nov-2002)
/dev/ad1s1 is not a block special device.
Proceed anyway? (y,n) y
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
# e2fsck -f /dev/ad1s1
e2fsck 1.32 (09-Nov-2002)
The filesystem size (according to the superblock) is 194560 blocks
The physical size of the device is 0 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
Error reading block 4 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore error<y>?
/dev/ad1s1: e2fsck canceled.
>Fix:
Not known.
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040220112557.7B02541AF>