On Thu, May 09, 2013 at 11:26:25AM +0200, Toralf Förster wrote: > I'm just curious why the last of the following 3 commands : > > $> dd if=/dev/zero of=/mnt/ramdisk/disk1 bs=1M count=257 > $> yes | /sbin/mkfs.btrfs /mnt/ramdisk/disk1 > $> mount -o loop /mnt/ramdisk/disk1 /mnt/t > > gives 3x the same log message : > > 2013-05-09T11:23:00.230+02:00 n22 kernel: device fsid > 5b4be7c4-e662-459a-a2a7-066e9384c901 devid 1 transid 4 /dev/loop1 > 2013-05-09T11:23:00.581+02:00 n22 kernel: device fsid > 5b4be7c4-e662-459a-a2a7-066e9384c901 devid 1 transid 4 /dev/loop1 > 2013-05-09T11:23:00.583+02:00 n22 kernel: device fsid > 5b4be7c4-e662-459a-a2a7-066e9384c901 devid 1 transid 4 /dev/loop1
At a guess, two of those are probably from btrfs dev scan triggered by udev. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Well, sir, the floor is yours. But remember, the --- roof is ours!
signature.asc
Description: Digital signature
