On Tue, Aug 12, 2003 at 09:40:49AM -0700, Shawn Ostapuk wrote:
> V pr0n State: up Plexes: 1 Size: 1172 GB
> P vinum0.p0 C State: corrupt Subdisks:11 Size: 1172 GB
> S vinum0.p0.s0 State: up PO:0 B Size:152 GB
>
On Wednesday, 20 August 2003 at 15:37:27 -0700, Shawn Ostapuk wrote:
>> Hmm. This is very strange. Try this:
>>
>> # vinum debug 8
>> # fsck ...
>> # vinum info -V
>>
>> I'd like to see the output of the info command.
>
> Nothing :(
>
> su-2.03# vinum debug 8
> su-2.03# fsck /dev/vinum/pr0
> Hmm. This is very strange. Try this:
>
> # vinum debug 8
> # fsck ...
> # vinum info -V
>
> I'd like to see the output of the info command.
Nothing :(
su-2.03# vinum debug 8
su-2.03# fsck /dev/vinum/pr0n
** /dev/vinum/pr0n
CANNOT READ: BLK 16
CONTINUE? [yn] n
su-2.03# vinum info
On Wednesday, 13 August 2003 at 19:03:21 -0700, Shawn Ostapuk wrote:
>>> su-2.03# vinum lv -r
>>> V pr0n State: up Plexes: 1 Size: 1172 GB
>>> ...
>>>
>>> Either method results in an umountable and unaccessable filesystem.
>>>
>>> su-2.03# mount /dev/vinum/pr0n /d
On Monday, 11 August 2003 at 21:41:00 -0700, Shawn Ostapuk wrote:
> I have an unusual (or at least usual problem for me) with vinum that
> I seem to be the only one suffering from.
>
> I'm running freebsd 4.8 RELEASE, generic kernel...
>
> I have about 10 drives making a terabyte or so with a simpl
> Vinum configs are additive. You shouldn't redefine things that Vinum
> already knows about. As far as I can see with a superficial look, all
> you need is:
>
> > drive vinumdrive10 device /dev/ad7e
> > sd name vinum0.p0.s10 drive vinumdrive10 size 0 plex vinum0.p0
Thanks, I'll remember th
On Tuesday, 12 August 2003 at 23:52:09 -0700, Shawn Ostapuk wrote:
> (Sorry for being so long, thought it would be less confusing and save
> additional questions to show complete vinum lists)
>
> At this point lv -r shows everything as up. same as above but with total
> size as 1172 GB. vinum list
On Tuesday, 12 August 2003 at 9:40:49 -0700, Shawn Ostapuk wrote:
>> Vinum configs are additive. You shouldn't redefine things that Vinum
>> already knows about. As far as I can see with a superficial look, all
>> you need is:
>>
>>> drive vinumdrive10 device /dev/ad7e
>>> sd name vinum0.p0.
> > su-2.03# vinum lv -r
> > V pr0n State: up Plexes: 1 Size: 1172 GB
> > P vinum0.p0 C State: up Subdisks:11 Size: 1172 GB
> > S vinum0.p0.s00 State: up PO:0 B Size:152 GB
> > S vinum0.p0.s01 State:
(Sorry for being so long, thought it would be less confusing and save
additional questions to show complete vinum lists)
> > su-2.03# vinum lv -r pr0n
> > V pr0n State: up Plexes: 1 Size: 1172 GB
> > P vinum0.p0 C State: corrupt Subdisks:11 Size:
10 matches
Mail list logo
