Btrfs devel - Jul 2012 - no dev_stats entry found / OK on first mount after mkfs

Hi,

after upgrading from 3.4.0 to 3.5.0-rc5 on this powerpc machine, the 
following is printed during bootup:

  [   18.630750] device fsid ce8c9df5-0a93-47c6-adf6-25084f352a4f devid 1
transid 11061 /dev/hda7
  [   18.637193] btrfs: disk space caching is enabled
  [   18.706423] btrfs: no dev_stats entry found for device /dev/hda7 (devid 1)
(OK on first mount after mkfs)

The btrfs on hda7 has been created many months ago and has been mounted 
several times since then. Assuming "first mount after mkfs" does not
apply
here, is it then NOT OK that no dev_stats entry has been found?

IOW: should I worry about this message?

Thanks,
Christian.
-- 
BOFH excuse #313:

your process is not ISO 9000 compliant
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On Mon, Jul 02, 2012 at 02:46:11PM -0700, Christian Kujau
wrote:
> Hi,
> 
> after upgrading from 3.4.0 to 3.5.0-rc5 on this powerpc machine, the 
> following is printed during bootup:
> 
>   [   18.630750] device fsid ce8c9df5-0a93-47c6-adf6-25084f352a4f devid 1
transid 11061 /dev/hda7
>   [   18.637193] btrfs: disk space caching is enabled
>   [   18.706423] btrfs: no dev_stats entry found for device /dev/hda7
(devid 1) (OK on first mount after mkfs)
> 
> The btrfs on hda7 has been created many months ago and has been mounted 
> several times since then. Assuming "first mount after mkfs" does
not apply
> here, is it then NOT OK that no dev_stats entry has been found?
> 
> IOW: should I worry about this message?
No, you should not.  If this is your first mount after upgrading your
kernel to the one with btrfs dev stats feature, "first mount after
mkfs"
sort of applies.

Thanks,

		Ilya
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On Tue, 3 Jul 2012 at 01:41, Ilya Dryomov wrote:
> > after upgrading from 3.4.0 to 3.5.0-rc5 on this powerpc machine, the 
> > following is printed during bootup:
> > 
> >   [   18.630750] device fsid ce8c9df5-0a93-47c6-adf6-25084f352a4f
devid 1 transid 11061 /dev/hda7
> >   [   18.637193] btrfs: disk space caching is enabled
> >   [   18.706423] btrfs: no dev_stats entry found for device /dev/hda7
(devid 1) (OK on first mount after mkfs)
> > 
> > The btrfs on hda7 has been created many months ago and has been
mounted
> > several times since then. Assuming "first mount after mkfs"
does not apply
> > here, is it then NOT OK that no dev_stats entry has been found?
> > 
> > IOW: should I worry about this message?
> 
> No, you should not.  If this is your first mount after upgrading your
> kernel to the one with btrfs dev stats feature, "first mount after
mkfs"
> sort of applies.
OK, this is what I''d hoped for :-) Maybe the message should read
"OK on
first mount after mkfs or kernel upgrade" - but then again nobody else got 
worried, so the current message is OK, I guess.

Thanks for replying,
Christian.
-- 
BOFH excuse #332:

suboptimal routing experience
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html