vinum ufs1 drives on freebsd 5.2.1

Greg 'groggy' Lehey grog at
Tue Jul 13 21:37:09 PDT 2004

On Tuesday, 13 July 2004 at 22:00:52 -0500, micko wrote:
> On Tue, Jul 13, 2004 at 08:06:50PM -0500, micko wrote:
>> On Wed, Jul 14, 2004 at 07:43:02AM +0930, Greg 'groggy' Lehey wrote:
>>> On Tuesday, 13 July 2004 at 16:30:17 -0500, micko wrote:
>>>> Hi, I just installed fbsd 5.2.1 on a system which
>>>> had fbsd 4.9 with a vinum ufs1 stripe. When I tried
>>>> to mount the vinum stripe on fbsd 5.2.1 it went ok, but
>>>> doing 'ls' gave me 'bad_dir' and a kernel panic. Doing
>>>> fsck gave me 'unknown filesystem type'. Seems like there
>>>> is no backwards compatibility.
>>> That conclusion is incorrect.
>>>> Can this somehow be saved or do I need to put the drives on a fbsd
>>>> 4.x system to get the data?
>>> You need to find out what the problem is first.  To do so, you should
>>> use the information at your disposal.  See
>>> for more details.
>> It turned out to be a failing drive, which now is totally dead. Is there
>> anyway to get some data out of the 1st part of the stripe?
> I found the problem. Originally when I was creating the partitions on the
> fbsd 4.x system I didn't slice up the drive, I used da0c/e. When using
> the drive under fbsd 5.x and devfs, the system brings up da0s1c/e. Is there
> anyway to override this behavior?

No.  Why do you want to?  And why is it a problem?

Note the warning in the man page:

     partition ``c'' represents the whole disk and should not be used
     for any other purpose.

I'm surprised you got it to work at all.  *That*'s a bug.

Note: I discard all HTML mail unseen.
Finger grog at for PGP public key.
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-fs mailing list