Re: vinum & fsck wrappers strangeness
On Sun, Oct 29, 2000, John W. De Boskey wrote: > Hi, > >I ran into an interesting gotcha with fsck and vinum... > >I have the following line in /etc/fstab: > > /dev/vinum/raid5/pubufs rw 2 2 > >and during an upgrade (old current to current), I commented the > line out during the reboot process. After bringing the new system > online, I executed: > > /sbin/fsck -y /dev/vinum/raid5 > > and received the following error: > > fsck: exec /usr/sbin/fsck_unused for /dev/vinum/raid5: No such file or directory OK. That means that the disklabel checks are failing for type 'vinum'. I'll take a look at this. What you should be doing is running fsck with a type, ie fsck -t ufs /dev/vinum/raid5 >So, it appears that fsck is attempting to determine a file > system type, tries to use /etc/fstab, and then falls back to > a secondary scheme. In the secondary scheme, ufs is what we want, > but vinum is what we're getting. > >If anyone has any information about this please let me know. I'll > try to look into it tomorrow. I'll try fix the autodetect for vinum partition types (if its possible, I seem to remember there being a vinum type in the header files). Its weird though, I would have thought a vinum device would be type FSTYPE (eg BSD4.3) rather than VINUM, which I'd associate with the underlying devices .. Adrian -- Adrian Chadd"Programming is like sex: <[EMAIL PROTECTED]> One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vinum & fsck wrappers strangeness
On Sun, 29 Oct 2000, John W. De Boskey wrote: >I ran into an interesting gotcha with fsck and vinum... > >I have the following line in /etc/fstab: > > /dev/vinum/raid5/pubufs rw 2 2 > >and during an upgrade (old current to current), I commented the > line out during the reboot process. After bringing the new system > online, I executed: > > /sbin/fsck -y /dev/vinum/raid5 > > and received the following error: > > fsck: exec /usr/sbin/fsck_unused for /dev/vinum/raid5: No such file or directory I saw a related problem with mfs. I had the following lines in /etc/fstab: --- #/dev/ad0s4 noneswapsw /dev/ad0s4 /tmpmfs rw,-s65536,-i8192,noatime,noauto --- The mfs line has very little to do with /dev/ad0s4 or swap. The label for /dev/ad0s4 just provides a (bogus) geometry for mfs. I wasn't using /dev/ad0s4 for either swap or mfs, but it happened to have a filesystem on it, and when I tried to fsck this, fsck attempted to exec the nonexistent file fsck_mfs. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vinum & fsck wrappers strangeness
Hi, I ran into an interesting gotcha with fsck and vinum... I have the following line in /etc/fstab: /dev/vinum/raid5/pubufs rw 2 2 and during an upgrade (old current to current), I commented the line out during the reboot process. After bringing the new system online, I executed: /sbin/fsck -y /dev/vinum/raid5 and received the following error: fsck: exec /usr/sbin/fsck_unused for /dev/vinum/raid5: No such file or directory Knowing that I've been able to fsck this volume in the past I checked for a vinum specific fsck binary. Nothing there. It then occurred to me it's a ufs volume, and I've always fsck'd it by mount point. I then uncommented the line in /etc/fstab and executed: /sbin/fsck -y /pub and it worked correctly. After the above (with the /etc/fstab line uncommented), I re-executed:o /sbin/fsck -y /dev/vinum/raid5 and it worked correctly. So, it appears that fsck is attempting to determine a file system type, tries to use /etc/fstab, and then falls back to a secondary scheme. In the secondary scheme, ufs is what we want, but vinum is what we're getting. If anyone has any information about this please let me know. I'll try to look into it tomorrow. Thanks, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
