Modify

Opened 4 years ago

Last modified 3 years ago

#14034 new defect

r37754:mkfs.ext4 fail to work

Reported by: ryd994@… Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: r37754 e2fsprogs mkfs Cc:

Description

root@OpenWrt:~# mkfs.ext4  /dev/sdb1
mke2fs 1.42.8 (20-Jun-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
456960 inodes, 1827840 blocks
91392 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1874853888
56 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done                            
mkfs.ext4: Invalid argument while zeroing block 1827824 at end of filesystem
Writing inode tables: done                            
Creating journal (32768 blocks): mkfs.ext4: Invalid argument 
        while trying to create journal

mkfs.ext3 seems not to be working also

root@OpenWrt:~# mkfs.ext3  /dev/sdb1
mke2fs 1.42.8 (20-Jun-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
456960 inodes, 1827840 blocks
91392 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1874853888
56 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done                            
mkfs.ext3: Invalid argument while zeroing block 1827824 at end of filesystem
Writing inode tables: 16/56
Could not write 6 blocks in inode table starting at 524290: Invalid argument

without journal doesn't help

root@OpenWrt:~# mkfs.ext4 -O ^has_journal /dev/sdb1
mke2fs 1.42.8 (20-Jun-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
456960 inodes, 1827840 blocks
91392 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1874853888
56 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done                            
mkfs.ext4: Invalid argument while zeroing block 1827824 at end of filesystem
Writing inode tables: done                            
Writing superblocks and filesystem accounting information:  0/56
Warning, had trouble writing out superblocks.

Filesystem seems not created/corrupted

root@OpenWrt:~# mount /dev/sdb1 /mnt
mount: mounting /dev/sdb1 on /mnt failed: Invalid argument

block-mount seems all right. I created filesystem on my laptop and the thumb drive works fine as extroot

Attachments (0)

Change History (9)

comment:1 follow-up: Changed 4 years ago by alphasparc@…

Did you format it using e2fsprogs?

comment:2 in reply to: ↑ 1 Changed 4 years ago by ryd994@…

Replying to alphasparc@…:

Did you format it using e2fsprogs?

Yes,e2fsprogs installed and mkfs.ext4 , which is an alias of mke2fs was used

comment:3 Changed 4 years ago by anonymous

I can confirm this in r37652
Same error here, small files as ext4-images seem to work though:

dd if=/dev/zero of=/tmp/test.img bs=1M count=8
mkfs.ext4 /tmp/test.img

comment:4 Changed 4 years ago by zorog@…

I can confirm this bug on r37789

comment:5 Changed 4 years ago by anonymous

I discovered resize2fs is broken too, while trying to make a workaround. (Create 8MB-ext4 and then resize it to full size)

resize2fs: Invalid argument while trying to resize /dev/sda1
Please run 'e2fsck -fy /dev/sda1' to fix the filesystem after the aborted resize operation.

comment:6 Changed 4 years ago by anonymous

The problem only appears for images/devices with more than 2048MB capacity.

resize2fs /dev/sda1 2048M # (2GB) This works without errors!

resize2fs /dev/sda1 2049M # (2GB + 1MB) This does _NOT_ work! ("resize2fs: Invalid argument while trying to resize /dev/sda1")

comment:7 Changed 4 years ago by anonymous

I met the bug too. my revision is r37789.
mke2fs and mount will work if the size is lower than 2048M, but not if over 2048M.

comment:8 Changed 4 years ago by anonymous

The revert from r37798 works, now >2GB format and resize is possible.

comment:9 Changed 3 years ago by freq

Same issue with mkfs.ext4 on 240GB SSD attached to banana pi r1.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.