Skip to contentSkip to conversation

syslog message repeated 3x

DISCUSSION Toralf Förster 3 participants 8 messages May 9, 2013 Btrfs file system

lore
Share & tools
lore
#0 lore raw

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
Signature · 3 lines
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
#1 lore raw
Quoted 11 lines · Toralf Förster

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.

Signature · 4 lines
=== 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!                              
#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · Hugo Mills

At a guess, two of those are probably from btrfs dev scan triggered by udev.

Those messages do only appear for a btrfs, not if I choose ext4.

- --
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlGLfHIACgkQhyrlCH22naPeEwCfcJxcJ3zGyeTiwdyYzKjIQlVG a4YAoLwo/FM50Pewp57VnATwY8cVBsQU
=ti4S
-----END PGP SIGNATURE-----

#3 lore raw
Quoted 7 lines · Toralf Förster

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 2 lines · Hugo Mills

At a guess, two of those are probably from btrfs dev scan triggered by udev.

Those messages do only appear for a btrfs, not if I choose ext4.

They're from the btrfs kernel module, so that's hardly surprising. :)

Hugo.

Signature · 4 lines
=== 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
   --- You know... I'm sure this code would seem a lot better if I ---   
                         never tried running it.                         
#4 lore raw
In reply to Toralf Förster

Hi,

I just try your steps, but only 1x log message.

Anyway, i use the latest btrfs-progs.
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git

Can you try this and see if it happens again?

Thanks,
Wang

Quoted 20 lines

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
Signature · 7 lines
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#5 lore raw

Oh, My kernel version is btrfs-next.

This message gets from kernel..so you can try this url:
git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git

Quoted 34 lines

Hi,

I just try your steps, but only 1x log message.

Anyway, i use the latest btrfs-progs.
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git

Can you try this and see if it happens again?

Thanks,
Wang

Quoted 20 lines

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
Signature · 7 lines
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#6 lore raw
In reply to Wang Shilong
Quoted 1 line · Wang Shilong

Anyway, i use the latest btrfs-progs.

well, under Gentoo I used sys-fs/btrfs-progs-9999 which points always to the latest git version :
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git

My host kernel is stable 3.9.1

The mount command still gives :

2013-05-09T14:43:35.604+02:00 n22 kernel: device fsid 20a30a6b-a82f-429f-b426-00f1739e4d3d devid 1 transid 8 /dev/loop1
2013-05-09T14:43:35.604+02:00 n22 kernel: device fsid 20a30a6b-a82f-429f-b426-00f1739e4d3d devid 1 transid 8 /dev/loop1
2013-05-09T14:43:35.608+02:00 n22 kernel: btrfs: disk space caching is enabled
2013-05-09T14:43:35.660+02:00 n22 kernel: device fsid 20a30a6b-a82f-429f-b426-00f1739e4d3d devid 1 transid 8 /dev/loop1
Signature · 3 lines
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
#7 lore raw
Quoted 6 lines · Toralf Förster
Quoted 1 line · Wang Shilong

Anyway, i use the latest btrfs-progs.

well, under Gentoo I used sys-fs/btrfs-progs-9999 which points always to the latest git version :
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git

Quoted 8 lines

My host kernel is stable 3.9.1

The mount command still gives :

2013-05-09T14:43:35.604+02:00 n22 kernel: device fsid 20a30a6b-a82f-429f-b426-00f1739e4d3d devid 1 transid 8 /dev/loop1
2013-05-09T14:43:35.604+02:00 n22 kernel: device fsid 20a30a6b-a82f-429f-b426-00f1739e4d3d devid 1 transid 8 /dev/loop1
2013-05-09T14:43:35.608+02:00 n22 kernel: btrfs: disk space caching is enabled
2013-05-09T14:43:35.660+02:00 n22 kernel: device fsid 20a30a6b-a82f-429f-b426-00f1739e4d3d devid 1 transid 8 /dev/loop1

I guess the main question is... why is this a problem for you?

The message is informational and doesn't indicate any kind of issue
with the FS. I'd just ignore it/them.

(Also, are you running btrfs dev scan beforehand or not? It'd be
interesting to see the difference in your logs -- particularly with timestamps -- when you do that.)

Hugo.

Signature · 3 lines
=== 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
     --- "I am the author. You are the audience. I outrank you!" ---