On Friday, 8 October 2004 at 14:52:48 +0200, Paul Everlund wrote:
> Greg 'groggy' Lehey wrote:
>> On Thursday, 7 October 2004 at 18:11:52 +0200, Paul Everlund wrote:
>> Can you be more specific?
>
> My vinum.conf looks like this, if this is to be more specific:
>
>drive ad5 device /dev/ad5s1e
Greg 'groggy' Lehey wrote:
On Thursday, 7 October 2004 at 18:11:52 +0200, Paul Everlund wrote:
> Hi Greg and list!
Thank you for your reply!
> I did have two 120 GB's disk drives in vinum as a striped raid.
Can you be more specific?
My vinum.conf looks like this, if this is to be more specific:
On Thursday, 7 October 2004 at 18:11:52 +0200, Paul Everlund wrote:
> Hi Greg and list!
>
> I did have two 120 GB's disk drives in vinum as a striped raid.
Can you be more specific?
> One disk crashed, and is not found during boot. It starts up and
> makes the usual noises, but then it stalls wi
Hi Greg and list!
I did have two 120 GB's disk drives in vinum as a striped raid.
One disk crashed, and is not found during boot. It starts up and
makes the usual noises, but then it stalls with a katjing, katjing
and so on. It seems like either the steering electronics, or the
read/write-heads mec
On Tuesday, 24 February 2004 at 8:56:58 +0100, Danny Carroll wrote:
>> No, that's not correct. It does happen if you choose too small a
>> stripe size, but that's the best reason for choosing larger stripes.
>> That's described in much detail in the man page.
>
> How can it not be correct? When
> No, that's not correct. It does happen if you choose too small a
> stripe size, but that's the best reason for choosing larger stripes.
> That's described in much detail in the man page.
How can it not be correct? When you write some data, it writes to all 4 disks,
when you read it reads from
On Tuesday, 24 February 2004 at 8:30:15 +0100, Danny Carroll wrote:
>>> vinum and ide on my system results is very poor disk performance, I
>>> see a 10-fold increase in read/write actions. I'll be interested in
>>> revisiting vinum with some SCSI disks sometime soon.
>>
>> How did you test it?
>
> We already discussed this. The likelihood of such far-reaching damage
> is low.
>
Hmmm ok..
> > I can't prove any of this since I urgently needed about 150gb of
> > space. So I re-formatted.
> >
> > Like I said it is a shame since I wanted to understand what happened
> > now, but, then again,
On Monday, 23 February 2004 at 12:44:19 +0100, Danny Carroll wrote:
> Greg,
>
> Thanks for all the responses. Unfortunatly I ran out of time and resorted to a
> restore of week old data. No big loss for me, but I really wanted to debug
> this to better understand what happened.
>
> I think it wen
Greg,
Thanks for all the responses. Unfortunatly I ran out of time and resorted to a
restore of week old data. No big loss for me, but I really wanted to debug
this to better understand what happened.
I think it went something like this:
ide drive crashes.
kernel panics (for this or some other
On Friday, 20 February 2004 at 9:22:21 +1100, Tony Frank wrote:
> Hi,
>
> On Thu, Feb 19, 2004 at 09:46:35AM +0100, Danny Carroll wrote:
>> Thanks for the information... I really need the space now so I am going to wipe
>> it and start from scratch, although I am not sure if I will use vinum agai
On Thursday, 19 February 2004 at 9:46:35 +0100, Danny Carroll wrote:
> Tony et al,..
>
> Thanks for the information... I really need the space now so I am going to wipe
> it and start from scratch, although I am not sure if I will use vinum again.
>
> I guess my main concern is that when one of m
On Thursday, 19 February 2004 at 1:04:29 +1100, Tony Frank wrote:
> Hi,
>
> On Wed, Feb 18, 2004 at 01:15:18PM +0100, Danny Carroll wrote:
>> Quoting Tony Frank <[EMAIL PROTECTED]>:
>
>>> So you have a subdisk down which means Vinum can still read from the plex
>>> but has to manually calculate th
On Wednesday, 18 February 2004 at 9:34:29 +0100, Danny Carroll wrote:
> Quoting Greg 'groggy' Lehey <[EMAIL PROTECTED]>:
>> I answered an almost identical question yesterday: it depends on the
>> volume structure, which you haven't stated. Look at
>> http://www.vinumvm.org/vinum/how-to-debug.html
Hi,
On Thu, Feb 19, 2004 at 09:46:35AM +0100, Danny Carroll wrote:
> Thanks for the information... I really need the space now so I am going to wipe
> it and start from scratch, although I am not sure if I will use vinum again.
>
> I guess my main concern is that when one of my disks crashed, th
Tony et al,..
Thanks for the information... I really need the space now so I am going to wipe
it and start from scratch, although I am not sure if I will use vinum again.
I guess my main concern is that when one of my disks crashed, the ufs filesystem
got corrupted and I really did not expect th
Hi,
On Wed, Feb 18, 2004 at 01:15:18PM +0100, Danny Carroll wrote:
> Quoting Tony Frank <[EMAIL PROTECTED]>:
> > So you have a subdisk down which means Vinum can still read from the plex
> > but has to manually calculate the missing subdisk data.
> But I assume it cant write till I replace it..
Quoting Tony Frank <[EMAIL PROTECTED]>:
> Ok, this is wrong - you really just want to define one vinum drive per
> physical device.
> Ie for a particular disk, give it a single 'vinum' partition using disklabel.
> Then use different subdisks to split your space up.
I was afraid of that Noted
Hi there,
On Wed, Feb 18, 2004 at 09:34:29AM +0100, Danny Carroll wrote:
> Quoting Greg 'groggy' Lehey <[EMAIL PROTECTED]>:
> > If this volume has only one plex, you're lost, unless you can bring up
> > the failed disk long enough to make a backup.
> Here is the output:
>
> 20 drives:
> D data1
Quoting Greg 'groggy' Lehey <[EMAIL PROTECTED]>:
> I answered an almost identical question yesterday: it depends on the
> volume structure, which you haven't stated. Look at
> http://www.vinumvm.org/vinum/how-to-debug.html and supply in
> particular the output of 'vinum list', unless the following
[Format recovered--see http://www.lemis.com/email/email-format.html]
Log output wrapped.
On Tuesday, 17 February 2004 at 14:27:51 +0100, Danny Carroll wrote:
> Hello,
>
> About 6 weeks ago one of the disks in my Vinum array crashed.
> However, the major problem is now that the file system is corr
Hello,
About 6 weeks ago one of the disks in my Vinum array crashed.
However, the major problem is now that the file system is corrupt. It
appears I have lost all of my 300Gb virtual disk...
This is what I found in the message log.
Jan 2 04:13:07 guard /kernel: ad4s1a: hard error reading fsbn
In <[EMAIL PROTECTED]>, Wojtek Bauman <[EMAIL PROTECTED]> typed:
> Hello!
>
> I've got a problem with my disk on FreeBSD. Few days ago I tried to mount
> a partition on /usr, but it told me that it's not clean and that
> I have to use fsck. So I tried, but then I saw this:
> THE FOLLOWING DISK SEC
Hello!
I've got a problem with my disk on FreeBSD. Few days ago I tried to mount
a partition on /usr, but it told me that it's not clean and that
I have to use fsck. So I tried, but then I saw this:
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 16, 17, 18, 19, 20, 21,
22, 23, 24, 25, 26, 27, 28,
24 matches
Mail list logo
