Hi all,
I tried to re-mkreiserfs /dev/md1 (RAID1) and got:
mkreiserfs: Guessing about desired format..
-- it's guessing, but not telling me the result :-(
Block 16 (0x901) contains super block of format 3.5 with standard journal
-- nope, it is 3.6 already
next try: mkreiserfs -v 3.6 /dev/md1
Block 16 (0x901) contains super block of format 3.6 with standard journal
-- That's ok now
[...]
Journal parameters:
Device [0x0]
Magic [0x66ada75d]
Size 8193 (including journal header) (first block 18)
Max transaction length 1024
Max batch size 900
Max commit age 30
Space reserved by journal: 0
No space for the journal? Hmmm... so I replied 'n' and tried
'mkreiserfs -v 3.6 -t 8192 /dev/md1' and got:
WARNING: wrong specified (or default) transactionmax size (8192).
Changed to 1024
-- that's ok according to the man page
Block 16 (0x901) contains super block of format 3.6 with non-standard journal
-- funny, now it's non-standard
[...]
Journal parameters:
Device [0x0]
Magic [0x5b7e8e89]
Size 8193 (including journal header) (first block 18)
Max transaction length 1024
Max batch size 900
Max commit age 30
Space reserved by journal: 8192
-- didn't it just tell me I could use a max. of 1024?
When trying '-t 1024' I get the same output as with a normal mkreiserfs (no
space reserved for journal).
So what's up here? Does it mean that a 'normal' mkreiserfs does not reserve
blocks for the journal? ('Space reserved by journal: 0')? And why do I get
several messages 'disk contains super block of format 3.[5|6] with
[non-]standard journal'?
In other words: which way is the best? I wish the man page and mkreiserfs
itself could tell me more.
BTW, version is reiserfsprogs 3.x.0k-pre9 (SuSE 7.3), kernel 2.4.13
Olaf
