Package: e2fsprogs
Version: 1.40.8-2
Severity: normal
/dev/mapper/vgbig-loebas is 6.1T, /dev/mapper/vg11-loebas--journal is 500M
[EMAIL PROTECTED]:~# mke2fs -L loebas -I 128 -j -J
device=/dev/mapper/vg11-loebas--journal -m 0 -O
large_file,dir_index,filetype,resize_inode /dev/mapper/vgbig-loebas
mke2fs 1.40.8 (13-Mar-2008)
mke2fs: File too large while trying to determine filesystem size
Removing the "-J device=/dev/mapper/vg11-loebas--journal" part lets
mke2fs continue:
[EMAIL PROTECTED]:~# mke2fs -L loebas -I 128 -j -m 0 -O
large_file,dir_index,filetype,resize_inode /dev/mapper/vgbig-loebas
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=loebas
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
409141248 inodes, 1636552704 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
49944 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-rc8
I've now dropped the internal journal:
[EMAIL PROTECTED]:~# tune2fs -O ^has_journal /dev/mapper/vgbig-loebas
tune2fs 1.40.8 (13-Mar-2008)
(That took almost as long as creating the filesystem in the first
place...)
Now trying to add the journal device gives a clue about what's wrong:
[EMAIL PROTECTED]:~# tune2fs -J device=/dev/mapper/vg11-loebas--journal
/dev/mapper/vgbig-loebas
tune2fs 1.40.8 (13-Mar-2008)
tune2fs: Filesystem has unexpected block size
while trying to open journal on /dev/mapper/vg11-loebas--journal
[EMAIL PROTECTED]:~# mke2fs -b 4096 -O journal_dev
/dev/mapper/vg11-loebas--journal
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
0 inodes, 128000 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
0 block group
32768 blocks per group, 32768 fragments per group
0 inodes per group
Superblock backups stored on blocks:
Zeroing journal device: done
[EMAIL PROTECTED]:~# tune2fs -J device=/dev/mapper/vg11-loebas--journal
/dev/mapper/vgbig-loebas
tune2fs 1.40.8 (13-Mar-2008)
Creating journal on device /dev/mapper/vg11-loebas--journal: done
This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Now it works...
Perhaps the error message given in the first case could be fixed so that
the blocksize problem becomes apparent at the beginning?
Thanks,
Paul Slootman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
