Hello On Wed, 2004-05-12 at 07:41, Andreas Dilger wrote: > On May 11, 2004 19:51 -0700, Clifford Beshers wrote: > > Thanks for the help everyone. In the end, it turned out that sfdisk is > > indeed the culprit. We created a 2.1T partition with fdisk, then asked > > sfdisk for the size and it said: -92,xxx,xxx. Unfortunately, this means > > we have to either fix it or find an alternate solution to creating > > partitions. If the word ``parted'' is on the tip of your tongue I'll > > bet you haven't actually used the thing... > > > > There were a few bugs of ours that acted as red herrings, but Linspire > > is now up and running on this system with ReiserFS 3 and kernel 2.6.5. > > > > While I'm here, I have some other questions: > > > > * What is the time complexity of mounting a ReiserFS partition? It > > seems to be proportional to the size of the partition? Is it > > different for Reiser4? > > AFAIK, reiserfs will do the initial zeroing of the journal and filesystem > bitmaps at the first mount time instead of at mkreiserfs time. I don't > know why it was done that way.
Hmm, I do not think that you are right. I guess reiserfs mount time is proportional to a partition size because reiserfs reads all bitmap blocks on mount. So does reiser4. > > > * Is there a tool to determine the type of file system on a > > partition without mounting it? > > Lots of them. "file -s /dev/foo" or if you have a newer e2fsprogs (1.33 > and newer I think) you can use "blkid [dev ...]" to tell you a bunch of > things about each device (LABEL, UUID, TYPE). > > Cheers, Andreas > -- > Andreas Dilger > http://sourceforge.net/projects/ext2resize/ > http://www-mddsp.enel.ucalgary.ca/People/adilger/ > >
