On Wed, Nov 17, 2010 at 10:09:04PM +1100, Joel Sing wrote: : > I think disklabel UIDs became largely usable around 5 months ago, however > there were still some major caveats especially with regards to disks that > were attached after boot. This was only addressed 2 months ago, which was > unfortunately after 4.8 had been tagged. Most of the remaining areas where > disklabel UIDs are not useable are slowly being addressed - hopefully over > the next few months there won't be too many places that they do not work.
Swell! Keep up the good work! > > > On Fri, Oct 15, 2010 at 08:57:36AM +0200, Jiri B. wrote: > > > > This works iff you list the partition by uid in /etc/fstab, e.g. > > > > > > > > $ uid=d3f6b8c752d5141a.a > > > > $ grep $uid /etc/fstab > > > > d3f6b8c752d5141a.a / ffs rw 1 1 > > > > $ fsck -f $uid > > > > ** /dev/wd0a (d3f6b8c752d5141a.a) (NO WRITE) > > > > ** Last Mounted on / > > > > ** Root file system > > > > ** Phase 1 - Check Blocks and Sizes > > > > ** Phase 2 - Check Pathnames > > > > ** Phase 3 - Check Connectivity > > > > ** Phase 4 - Check Reference Counts > > > > ** Phase 5 - Check Cyl groups > > > > 4270 files, 57007 used, 21613 free (1093 frags, 2565 blocks, 1.4% > > > > > > fragmentation) > > > > > > > If the fstab entry uses /dev/Xd0a format then it fails as reported. > > > > > > I don't see reason why `fsck -f' (or without -f) should depend on > > > /etc/fstab. It's not preen mode. > > > > > > I discovered this because I use softraid crypto and having 'fs_passno' > > > equal to 0 in > > > fstab, then doing fsck stuff later, after bringing up devices with > > > passfile... > > > > > > jirib > > -- > > "Stop assuming that systems are secure unless demonstrated insecure; > start assuming that systems are insecure unless designed securely." > - Bruce Schneier -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
