Since UFS labels were introduced, I've got strange behaviour when
fsck-ing or mounting my UFS partitions. Here is the console output at
boot :
GEOM_LABEL: Label for provider ad0s4 is ext2fs/PH4T.
GEOM_LABEL: Label for provider ad0s1a is ufsid/4867d45fa24cf28b.
GEOM_LABEL: Label for provider ad0s1d is ufsid/4867d45fd76f0998.
GEOM_LABEL: Label for provider ad0s1e is ufsid/4867d45fd3972203.
GEOM_LABEL: Label for provider ad0s1f is ufsid/4867d45f6ac00d3f.
GEOM_LABEL: Label for provider ad0s1g is ufsid/4867d45f91eb4111.
GEOM_LABEL: Label for provider ad0s3a is ufsid/48b16a479410599a.
Root mount waiting for: usbus7 usbus6 usbus5 usbus4 usbus3 usbus2 usbus1 usbus0
[snip]
Trying to mount root from ufs:/dev/ad0s1a
ugen5.2: <OmniVision> at usbus5
ugen6.2: <Microsoft> at usbus6
GEOM_LABEL: Label ufsid/4867d45fa24cf28b removed.
ums0: <Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), class
0/0, rev 1.10/3.00, addr 2> on usbus6
GEOM_LABEL: Label for provider ad0s1a is ufsid/4867d45fa24cf28b.
ums0: 5 buttons and [XYZ] coordinates
GEOM_LABEL: Label ufsid/4867d45fd76f0998 removed.
GEOM_LABEL: Label for provider ad0s1d is ufsid/4867d45fd76f0998.
GEOM_LABEL: Label ufsid/4867d45fd3972203 removed.
GEOM_LABEL: Label for provider ad0s1e is ufsid/4867d45fd3972203.
GEOM_LABEL: Label ufsid/4867d45f6ac00d3f removed.
GEOM_LABEL: Label for provider ad0s1f is ufsid/4867d45f6ac00d3f.
GEOM_LABEL: Label ufsid/4867d45f91eb4111 removed.
GEOM_LABEL: Label for provider ad0s1g is ufsid/4867d45f91eb4111.
GEOM_LABEL: Label ufsid/48b16a479410599a removed.
GEOM_LABEL: Label for provider ad0s3a is ufsid/48b16a479410599a.
WARNING: TMPFS is considered to be a highly experimental feature in FreeBSD.
GEOM_LABEL: Label ufsid/4867d45fd76f0998 removed.
GEOM_LABEL: Label ufsid/4867d45f6ac00d3f removed.
GEOM_LABEL: Label ufsid/4867d45f91eb4111 removed.
Notice the removal of UFS labels (the first removals appear during
"fsck -p" and the latter during mount). Then, in multi or single user,
here is what I've got when remounting read-write or read-only (my root
partition is mounted read-only at boot) :
[20:19] root@q 167 ~# mount -u -o rw /
GEOM_LABEL: Label ufsid/4867d45fa24cf28b removed.
[20:19] root@q 169 ~# mount -u -o ro /
GEOM_LABEL: Label for provider ad0s1a is ufsid/4867d45fa24cf28b.
[20:19] root@q 170 ~# ll /dev/ufsid/
total 1
145 dr-xr-xr-x 2 root wheel - 512 31 mar 20:08 ./
2 dr-xr-xr-x 8 root wheel - 512 31 mar 20:08 ../
153 crw-r----- 1 root operator - 0, 153 31 mar 20:18 4867d45fa24cf28b
120 crw-r----- 1 root operator - 0, 120 31 mar 20:08 4867d45fd3972203
123 crw-r----- 1 root operator - 0, 123 31 mar 20:08 48b16a479410599a
[20:20] root@q 171 ~# mount
/dev/ad0s1a on / (ufs, local, read-only)
devfs on /dev (devfs, local)
tmpfs on /tmp (tmpfs, local)
/dev/ad0s1d on /var (ufs, local, soft-updates)
/dev/ad0s1e on /usr/local (ufs, local, noatime, read-only)
/dev/ad0s1f on /usr/home (ufs, local, soft-updates)
/dev/ad0s1g on /work (ufs, local, soft-updates)
/dev/ad0s3a on /data (ufs, local, noatime, read-only)
[20:23] root@q 176 ~# kldstat | grep geom
4 1 0xffffffff807bf000 7cf8 geom_label.ko
29 1 0xffffffff80a6d000 4fb8 geom_part_gpt.ko
[20:23] root@q 177 ~# uname -a
FreeBSD q.gid0.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r190594M: Tue
Mar 31 19:10:02 CEST 2009
ro...@q.gid0.org:/work/obj/work/src/sys/QUAD amd64
Is this expected ?
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oli...@gid0.org - against HTML email & vCards X
www: http://www.gid0.org - against proprietary attachments / \
"Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas."
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
Olivier SMEDTS wrote:
> Hi,
>=20
> Since UFS labels were introduced, I've got strange behaviour when
> fsck-ing or mounting my UFS partitions. Here is the console output at
> boot :
> Is this expected ?
I didn't read your message in detail but if are you asking if the "label
=2E.. removed" are valid when the device is opened from an "alternative"
entry point (e.g. ad0s1e instead of ufsid/4867d45fd3972203) then yes,
this is by design. The label is read from the file system metadata and
anything that opens that file system for its own use can change this
metadata - so the labels are removed.
(note that this is nothing special as far as GEOM_LABEL is concerned -
this is present in all types and forms of labels).
If you're complaining about the verbosity of the whole process then I
think you can set the kern.geom.label.debug sysctl to -1 to avoid these
messages.
The "modern" way would be to use the labels as device nodes for mounting
instead of raw devices - in this case they would "stay" when opened.
--------------enig0AF00B832FA1D7C0D6D217CF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknVHyUACgkQldnAQVacBchuxACgg2GuKaEpeb+2Lrr10lKWbgQU
eoMAn2n+UWZ/H1UPvf01zuXlRWraGd//
=J3jT
-----END PGP SIGNATURE-----
--------------enig0AF00B832FA1D7C0D6D217CF--