[Bugme-new] [Bug 11246] New: extracting the tar file from ext3 to ext4 gives an error

bugme-daemon at bugzilla.kernel.org bugme-daemon at bugzilla.kernel.org
Sun Aug 3 23:24:27 PDT 2008 

http://bugzilla.kernel.org/show_bug.cgi?id=11246

           Summary: extracting the tar file from ext3 to ext4 gives an error
           Product: File System
           Version: 2.5
     KernelVersion: 2.6.27-rc1
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4 at kernel-bugs.osdl.org
        ReportedBy: disaster2008 at gmail.com
                CC: cmm at us.ibm.com


Latest working kernel version:
2.6.27-rc1
Earliest failing kernel version:
Distribution:
RHEL5.2
Hardware Environment:
i386

Problem Description:
extraction of tar file to ext4 from ext3 gives and error

Steps to reproduce:
1> created a tar file to ext3 filesystem on /dev/sda harddisk.

[root at e326 tmpmount]# mount
/dev/sda2 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext2 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

[root at e326 tmpmount]# ls -l /root/ext4-testcases/
total 65960
-rw-r--r--  1 root root     8041 Jul 14 16:38 fsx.tar.gz
[root at e326 tmpmount]#

2> create logical volume partition on different disk with following execution
of commands. e.g:
 1025  pvcreate /dev/sdb5
 1026  pvdisplay
 1027  pvdisplay /dev/sdb5
 1028  vgcreate mynew_vg /dev/sdb5
 1029  vgdisplay
 1030  lvcreate -L 4G -n vol01 mynew_vg
 1031  lvdisplay
 1032  fdisk -l
 1033  lvdisplay
 1034  cd ext4-testcases/e2fsprogs
 1035  ls
 1036  cd build/tmp/sbin/
 1037  ls
 1038  ./mke2fs -E test_fs -j -I 256 -b 1024 -O extents /dev/mynew_vg/vol01
 1039  mount -t ext4dev -o extents /dev/mynew_vg/vol01 /mnt/tmpmount
 1040  dmesg
 1041  mount -t ext4dev /dev/mynew_vg/vol01 /mnt/tmpmount

4> cd /mnt/tmpmount
5> [root at e326 tmpmount]# tar -zxvf /root/ext4-testcases/fsx.tar.gz
fsx/
tar: fsx: Cannot mkdir: Input/output error
fsx/fsx-linux.c
tar: fsx/fsx-linux.c: Cannot open: No such file or directory
fsx/slacker.h
tar: Error exit delayed from previous errors
[root at e326 tmpmount]#

Note: 

a> This error is not coming when i extract the tar file from ext3 filesystem.
e.g:
[root at e326 ext4-testcases]# pwd
/root/ext4-testcases
[root at e326 ext4-testcases]# tar -zxvf fsx.tar.gz
fsx/
fsx/fsx-linux.c
fsx/slacker.h
[root at e326 ext4-testcases]# cd /mnt/tmpmount/

b> This error is not occuring when i mount the ext4 filesystem with fdisk, it
seems only it is happening with when i create partition with lvmcreate.

Additional Info:

[root at e326 tmpmount]# dmesg | tail -n 50
SELinux: initialized (dev dm-0, type ext4dev), uses xattr
EXT4-fs: mballoc: 0 blocks 0 reqs (0 success)
EXT4-fs: mballoc: 0 extents scanned, 0 goal hits, 0 2^N hits, 0 breaks, 0 lost
EXT4-fs: mballoc: 0 generated and it took 0
EXT4-fs: mballoc: 0 preallocated, 0 discarded
kjournald2 starting.  Commit interval 5 seconds
EXT4 FS on dm-0, internal journal
EXT4-fs: mounted filesystem with ordered data mode.
EXT4-fs: delayed allocation enabled
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
SELinux: initialized (dev dm-0, type ext4dev), uses xattr
JBD: barrier-based sync failed on dm-0 - disabling barriers
attempt to access beyond end of device
dm-0: rw=0, want=20283398, limit=8388608
EXT4-fs error (device dm-0): ext4_read_inode_bitmap: Cannot read inode bitmap -
block_group = 1238, inode_bitmap = 10141698
EXT4-fs error (device dm-0) in ext4_new_inode: IO failure
attempt to access beyond end of device
dm-0: rw=0, want=8962054, limit=8388608
EXT4-fs error (device dm-0): ext4_read_inode_bitmap: Cannot read inode bitmap -
block_group = 547, inode_bitmap = 4481026
EXT4-fs error (device dm-0) in ext4_new_inode: IO failure
attempt to access beyond end of device
dm-0: rw=0, want=21069830, limit=8388608
EXT4-fs error (device dm-0): ext4_read_inode_bitmap: Cannot read inode bitmap -
block_group = 1286, inode_bitmap = 10534914
EXT4-fs error (device dm-0) in ext4_new_inode: IO failure
attempt to access beyond end of device
dm-0: rw=0, want=14237702, limit=8388608
EXT4-fs error (device dm-0): ext4_read_inode_bitmap: Cannot read inode bitmap -
block_group = 869, inode_bitmap = 7118850
EXT4-fs error (device dm-0) in ext4_new_inode: IO failure
EXT4-fs: mballoc: 216937 blocks 4118 reqs (1042 success)
EXT4-fs: mballoc: 12240 extents scanned, 521 goal hits, 1304 2^N hits, 0
breaks, 0 lost
EXT4-fs: mballoc: 156 generated and it took 352862
EXT4-fs: mballoc: 2442814 preallocated, 2409778 discarded
sd 0:0:1:0: [sdb] 143374000 512-byte hardware sectors (73407 MB)
sd 0:0:1:0: [sdb] Write Protect is off
sd 0:0:1:0: [sdb] Mode Sense: cf 00 00 08
sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support
DPO or FUA
 sdb: sdb1 < sdb5 >
sd 0:0:1:0: [sdb] 143374000 512-byte hardware sectors (73407 MB)
sd 0:0:1:0: [sdb] Write Protect is off
sd 0:0:1:0: [sdb] Mode Sense: cf 00 00 08
sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support
DPO or FUA
 sdb: sdb1 < sdb5 >
kjournald2 starting.  Commit interval 5 seconds
EXT4 FS on sdb5, internal journal
EXT4-fs: mounted filesystem with ordered data mode.
EXT4-fs: delayed allocation enabled
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
SELinux: initialized (dev sdb5, type ext4dev), uses xattr
[root at e326 tmpmount]#


Here is the /var/log/messages :

[root at e326 tmpmount]# cat /var/log/messages | tail -n 50
Aug  4 10:52:34 e326 kernel: EXT4-fs: mballoc: 0 blocks 0 reqs (0 success)
Aug  4 10:52:34 e326 kernel: EXT4-fs: mballoc: 0 extents scanned, 0 goal hits,
0 2^N hits, 0 breaks, 0 lost
Aug  4 10:52:34 e326 kernel: EXT4-fs: mballoc: 0 generated and it took 0
Aug  4 10:52:34 e326 kernel: EXT4-fs: mballoc: 0 preallocated, 0 discarded
Aug  4 10:59:27 e326 kernel: kjournald2 starting.  Commit interval 5 seconds
Aug  4 10:59:27 e326 kernel: EXT4 FS on dm-0, internal journal
Aug  4 10:59:27 e326 kernel: EXT4-fs: mounted filesystem with ordered data
mode.
Aug  4 10:59:27 e326 kernel: EXT4-fs: delayed allocation enabled
Aug  4 10:59:27 e326 kernel: EXT4-fs: file extents enabled
Aug  4 10:59:27 e326 kernel: EXT4-fs: mballoc enabled
Aug  4 10:59:36 e326 kernel: JBD: barrier-based sync failed on dm-0 - disabling
barriers
Aug  4 11:04:07 e326 kernel: attempt to access beyond end of device
Aug  4 11:04:07 e326 kernel: dm-0: rw=0, want=20283398, limit=8388608
Aug  4 11:04:07 e326 kernel: EXT4-fs error (device dm-0):
ext4_read_inode_bitmap: Cannot read inode bitmap - block_group = 1238,
inode_bitmap = 10141698
Aug  4 11:04:07 e326 kernel: EXT4-fs error (device dm-0) in ext4_new_inode: IO
failure
Aug  4 11:06:48 e326 kernel: attempt to access beyond end of device
Aug  4 11:06:48 e326 kernel: dm-0: rw=0, want=8962054, limit=8388608
Aug  4 11:06:48 e326 kernel: EXT4-fs error (device dm-0):
ext4_read_inode_bitmap: Cannot read inode bitmap - block_group = 547,
inode_bitmap = 4481026
Aug  4 11:06:48 e326 kernel: EXT4-fs error (device dm-0) in ext4_new_inode: IO
failure
Aug  4 11:07:39 e326 kernel: attempt to access beyond end of device
Aug  4 11:07:39 e326 kernel: dm-0: rw=0, want=21069830, limit=8388608
Aug  4 11:07:39 e326 kernel: EXT4-fs error (device dm-0):
ext4_read_inode_bitmap: Cannot read inode bitmap - block_group = 1286,
inode_bitmap = 10534914
Aug  4 11:07:39 e326 kernel: EXT4-fs error (device dm-0) in ext4_new_inode: IO
failure
Aug  4 11:07:39 e326 kernel: attempt to access beyond end of device
Aug  4 11:07:39 e326 kernel: dm-0: rw=0, want=14237702, limit=8388608
Aug  4 11:07:40 e326 kernel: EXT4-fs error (device dm-0):
ext4_read_inode_bitmap: Cannot read inode bitmap - block_group = 869,
inode_bitmap = 7118850
Aug  4 11:07:40 e326 kernel: EXT4-fs error (device dm-0) in ext4_new_inode: IO
failure
Aug  4 11:16:28 e326 avahi-daemon[8176]: recvmsg(): Resource temporarily
unavailable
Aug  4 11:30:05 e326 avahi-daemon[8176]: recvmsg(): Resource temporarily
unavailable
Aug  4 11:33:49 e326 avahi-daemon[8176]: recvmsg(): Resource temporarily
unavailable
Aug  4 11:33:54 e326 last message repeated 11 times
Aug  4 11:36:58 e326 kernel: EXT4-fs: mballoc: 216937 blocks 4118 reqs (1042
success)
Aug  4 11:36:58 e326 kernel: EXT4-fs: mballoc: 12240 extents scanned, 521 goal
hits, 1304 2^N hits, 0 breaks, 0 lost
Aug  4 11:36:58 e326 kernel: EXT4-fs: mballoc: 156 generated and it took 352862
Aug  4 11:36:58 e326 kernel: EXT4-fs: mballoc: 2442814 preallocated, 2409778
discarded
Aug  4 11:37:57 e326 kernel: sd 0:0:1:0: [sdb] 143374000 512-byte hardware
sectors (73407 MB)
Aug  4 11:37:57 e326 kernel: sd 0:0:1:0: [sdb] Write Protect is off
Aug  4 11:37:57 e326 kernel: sd 0:0:1:0: [sdb] Write cache: disabled, read
cache: enabled, doesn't support DPO or FUA
Aug  4 11:37:57 e326 kernel:  sdb: sdb1 < sdb5 >
Aug  4 11:37:59 e326 kernel: sd 0:0:1:0: [sdb] 143374000 512-byte hardware
sectors (73407 MB)
Aug  4 11:37:59 e326 kernel: sd 0:0:1:0: [sdb] Write Protect is off
Aug  4 11:37:59 e326 kernel: sd 0:0:1:0: [sdb] Write cache: disabled, read
cache: enabled, doesn't support DPO or FUA
Aug  4 11:37:59 e326 kernel:  sdb: sdb1 < sdb5 >
Aug  4 11:41:23 e326 kernel: kjournald2 starting.  Commit interval 5 seconds
Aug  4 11:41:23 e326 kernel: EXT4 FS on sdb5, internal journal
Aug  4 11:41:23 e326 kernel: EXT4-fs: mounted filesystem with ordered data
mode.
Aug  4 11:41:23 e326 kernel: EXT4-fs: delayed allocation enabled
Aug  4 11:41:23 e326 kernel: EXT4-fs: file extents enabled
Aug  4 11:41:23 e326 kernel: EXT4-fs: mballoc enabled
Aug  4 11:43:29 e326 avahi-daemon[8176]: recvmsg(): Resource temporarily
unavailable


Please let me know if you need some more info.

Thanks
-Rishi


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

More information about the Bugme-new mailing list