On Mon 30 Jun 2008, Theodore Tso wrote: > > So what happened is that you created the external journal with some > blocksize other than 4k. I'm guessing 1k, perhaps? There is a
Probably, yes. > requirement that the blocksize of the external journal device matches > the blocksize of the filesystem using the external journal device. So > what mke2fs tries to do helpfully is to create new filesystem with the > blocksize used by the external journal device, if it exists. So when > you specified -J device=/dev/mapper/vg11-loebas--journal, it did an > implicit -b 1024. Unfortunately, with a 6.1T filesystem, using a 1k > blocksize, the number of blocks needed to cover 6.1T don't fit in > 2**32 blocks. > > You're right, we should have better error message for this case. > > I'm curious though --- why did you create the external journal with a > 1k blocksize? Was this deliberate? Or accidental? I created the external journal without specifying the blocksize, not realizing that I needed to. Perhaps the blocksize parameter should be mandatory when creating an external journal... Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
