Date: Thu, 04 May 2000 16:51:37 +0200 From: Kenneth Karoliussen <kenneth@activeisp.com> To: Nadav Eiron <nadav@cs.technion.ac.il> Cc: freebsd-questions@freebsd.org Subject: Re: fsck and Vinum file systems Message-ID: <39118E79.F615BD65@activeisp.com> References: <Pine.GSO.3.95-heb-2.07.1000504171137.19074A-100000@csd>
next in thread | previous in thread | raw e-mail | index | archive | help
> My answer is valid for 3.4 (I don't run vinum on 4.0 yet, but I'm sure > it's pretty much the same). From man fstab(5) (on a 3.4 system, FWIW): > [snip] ... If > the sixth field is not present or is zero, a value of zero is returned > and fsck(8) will assume that the filesystem does not need to be checked. Actually I now about the sixth field, and it was intentionally set to disable the automatic device check.. The problem may perhaps be related to the basic configuration of the vinum device: fsck -p /dev/vinum/vol/pz1 Can't stat /dev/vinum/vol/rpz1: No such file or directory /dev/vinum/vol/pz1: /dev/vinum/vol/pz1 is not a character device /dev/vinum/vol/pz1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Any idea why the raw mode device of /dev/vinum/vol/pz1 does not exist? I have no raw mode device in a similar configuration on a 4.0-STABLE system. And the strange thing is that fsck does not complain about it missing.. /Kenneth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39118E79.F615BD65>