strange ramdrive behaviour

[Bgs <bgs@bgs.hu>]

 Hi all,

 I have a ramdrive set up at boot time. The script is very simple, sets 
up the filesystem and mounts the ramdrive. The interesting part is that 
at first it doesn't work, but run a second time it is fine.

At first the mkfs part is ok, but mount reports no fs.
The second time, mkfs part is ok again and mount works as well.

I sent to syslog the output of the first run:

Oct 13 02:26:28 wh-db02 ramdisk: Guessing about desired format.. Kernel 
2.6.13.4 is running.
Oct 13 02:26:28 wh-db02 ramdisk: Format 3.6 with standard journal
Oct 13 02:26:28 wh-db02 ramdisk: Count of blocks on the device: 16368
Oct 13 02:26:28 wh-db02 ramdisk: Number of blocks consumed by mkreiserfs 
formatting process: 8212
Oct 13 02:26:28 wh-db02 ramdisk: Blocksize: 4096
Oct 13 02:26:28 wh-db02 ramdisk: Hash function used to sort names: "r5"
Oct 13 02:26:28 wh-db02 ramdisk: Journal Size 8193 blocks (first block 18)
Oct 13 02:26:28 wh-db02 ramdisk: Journal Max transaction length 1024
Oct 13 02:26:28 wh-db02 ramdisk: inode generation number: 0
Oct 13 02:26:28 wh-db02 ramdisk: UUID: 2a989bfb-8380-4c28-b3d9-db57fc0049ec
Oct 13 02:26:28 wh-db02 ramdisk: Initializing journal - 
0%....20%....40%....60%....80%....100%
Oct 13 02:26:28 wh-db02 ramdisk: Syncing..ok
Oct 13 02:26:28 wh-db02 ramdisk:
Oct 13 02:26:28 wh-db02 ramdisk: Tell your friends to use a kernel based 
on 2.4.18 or later, and especially not a
Oct 13 02:26:28 wh-db02 ramdisk: kernel based on 2.4.9, when you use 
reiserFS. Have fun.
Oct 13 02:26:28 wh-db02 ramdisk:
Oct 13 02:26:28 wh-db02 ramdisk: ReiserFS is successfully created on 
/dev/ram0.
Oct 13 02:26:28 wh-db02 kernel: ReiserFS: ram0: warning: sh-2011: 
read_super_block: can't find a reiserfs filesystem on (dev ram0, block 
16, size 4096)
Oct 13 02:26:28 wh-db02 kernel:
Oct 13 02:26:28 wh-db02 kernel: ReiserFS: ram0: warning: sh-2021: 
reiserfs_fill_super: can not find reiserfs on ram0

Any ideas about the hysteresis? :)

Bye
Bgs

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/