Date: Wed, 17 Aug 2011 08:17:08 +0400 From: "Andrey V. Elsukov" <bu7cher@yandex.ru> To: Mark Saad <nonesuch@longcount.org> Cc: freebsd-hackers@freebsd.org Subject: Re: glabel on 9-BETA1 Message-ID: <4E4B40C4.6080608@yandex.ru> In-Reply-To: <CAMXt9NboLSTSRqZW2ZUD=BWdq7agbZFA6UeLrB_oOSSGbw%2BuwQ@mail.gmail.com> References: <CAMXt9NboLSTSRqZW2ZUD=BWdq7agbZFA6UeLrB_oOSSGbw%2BuwQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 17.08.2011 0:10, Mark Saad wrote: > root@blindness:~# glabel label rootfs ada0p4 > glabel: Can't store metadata on ada0p4: Operation not permitted. > > In 7.2 and prior there was a sysctl that could be tweaked to allow for > this to work , kern.geom.debugflag set to 16 would allow this to work. > > So my question is this. Should there be any reason why "glabel label > name device" on the root slice cause an issue > when the slice is mounted rw ? > > Is this a bug ? No. It isn't. When you are doing `glabel label` you overwriting last sector of given device with glabel's metadata. So you potentially can destroy some data in it. Using kern.geom.debugflags=16 is a bad practice. The right way is creating label before creation of file system and installing OS. Also you can use UFS labels (see tunefs(8)). -- WBR, Andrey V. Elsukov [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJOS0DKAAoJEAHF6gQQyKF6EHQH/jVhZ3GncKOl4111ct1o8NCh RSWezNT+7yjLK82U5NmXjq3hrhS3fLPDtBnwANngIGriXpiheBncE/6fj/HGvMsJ IZBIlAyJIgAQXQ8DS0Z19YSLKwq5fFNYh1wYMLXyhTt+5Q62cbX/ceRkppFbsxVt kjUM9aDnTGQZdlfFvhOsU6YOIP/53iv0d8eNGhUyOh2Dc7PIZnq8wyrr7j7+cSGX YjAd9S22UrX4tWt4svsnAP5eThTk4QP4Aj93SrDS/jj2pCfEt3z4s5SujzyPSPvx BJKNqmihy72UhTJ2hppgx3qVnvDtIaM9Jza2VHks4o+SXlFbUvdwMi7/4T2PifI= =0U0U -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E4B40C4.6080608>