Date: Tue, 14 Apr 2009 14:01:05 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-geom@freebsd.org Subject: Re: glabel: newfs vs tunefs Message-ID: <gs1tu5$eut$1@ger.gmane.org> In-Reply-To: <49E46F44.30606@icyb.net.ua> References: <49E46F44.30606@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB4D4DB6D2E59C59EF0EC8E56 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Andriy Gapon wrote: > I am not 100% sure, but it seems that glabel detects newfs -L labels ve= ry well, > but doesn't see labels set by tunefs -L. I am not sure if ths happens a= lways or > "sometimes". > Also, I used tunefs without -A option (it's documented as "potentially > dangerous"). So could it possibly be that tunefs updates one copy of su= perblock, > but glabel checks some other? Glabel checks superblocks in the order defined in ufs/ffs/fs.h : 68 #define SBLOCK_FLOPPY 0 69 #define SBLOCK_UFS1 8192 70 #define SBLOCK_UFS2 65536 71 #define SBLOCK_PIGGY 262144 72 #define SBLOCKSIZE 8192 73 #define SBLOCKSEARCH \ 74 { SBLOCK_UFS2, SBLOCK_UFS1, SBLOCK_FLOPPY, SBLOCK_PIGGY, -1 }= So it's theoretically possible that tunefs modifies the old (UFS1) location... --------------enigB4D4DB6D2E59C59EF0EC8E56 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.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ5HsIldnAQVacBcgRAvmzAJ9WvUMt2r+bMLFHuDB/xq0UaYOjiACg/nvh ragQmvwiahoi80b9ZgQ8YZk= =p3yd -----END PGP SIGNATURE----- --------------enigB4D4DB6D2E59C59EF0EC8E56--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gs1tu5$eut$1>