On Wednesday, 4 December 2002 at 14:30:10 -0400, Marc G. Fournier wrote:
> On Wed, 4 Dec 2002, Adam Laurie wrote:
>
>> .. having now digested what youve said so far, and re-read the docco
>> several times, i'm guessing the final step would be:
>>
>>6. Run
On Wednesday, 4 December 2002 at 9:36:29 +, Adam Laurie wrote:
> Adam Laurie wrote:
>> Greg 'groggy' Lehey wrote:
>>
>>>>
>>>> describe the procedure for unplugging the external chassis from
>>>> machine A, and plugging it i
On Saturday, 30 November 2002 at 8:39:44 +, Adam Laurie wrote:
> Greg 'groggy' Lehey wrote:
>
>>>
>>> describe the procedure for unplugging the external chassis from
>>> machine A, and plugging it into machine B, and bringing up the vinum
>>&
On Wed, Dec 04, 2002 at 02:30:10PM -0400, "Marc G. Fournier"
<[EMAIL PROTECTED]> wrote:
> On Wed, 4 Dec 2002, Adam Laurie wrote:
>
> > .. having now digested what youve said so far, and re-read the docco
> > several times, i'm guessing the final step wou
On Wed, 4 Dec 2002, Adam Laurie wrote:
> .. having now digested what youve said so far, and re-read the docco
> several times, i'm guessing the final step would be:
>
>6. Run 'vinum makedev'
>
> in which case our mistake was doing this and 'vinum start&#
Greg 'groggy' Lehey wrote:
describe the procedure for unplugging the external chassis from
machine A, and plugging it into machine B, and bringing up the vinum
RAID without re-initialising it (i.e. preserving the data already on
it).
1. On machine A, stop Vinum. Depending on th
Adam Laurie wrote:
Greg 'groggy' Lehey wrote:
describe the procedure for unplugging the external chassis from
machine A, and plugging it into machine B, and bringing up the vinum
RAID without re-initialising it (i.e. preserving the data already on
it).
1. On machine A,
a drive in the RAID, it was replacing the root disk. the
>>> system booted off a seperate stand alone root disk. the RAID is
>>> entirely independant of the root/boot drive.
>>
>> Yes, you're certainly not making yourself clear. Why did you need to
>> do anyth
D, it was replacing the root disk. the
system booted off a seperate stand alone root disk. the RAID is entirely
independant of the root/boot drive.
Yes, you're certainly not making yourself clear. Why did you need to
do anything? In a previous message you stated that you did a 'vinum
cre
lf clear... my problem wasn't
> replacing a drive in the RAID, it was replacing the root disk. the
> system booted off a seperate stand alone root disk. the RAID is entirely
> independant of the root/boot drive.
Yes, you're certainly not making yourself clear. Why did you need
Greg 'groggy' Lehey wrote:
yep. like all the others i've found, this deals with fixing problems
within the raid itself, not moving a working raid onto a new system
(which is effectively what i was doing).
No, it addresses exactly your problem, modulo the fact that your
plexes were RAID-5. I'
On Tuesday, 26 November 2002 at 10:58:15 +, Adam Laurie wrote:
> Greg 'groggy' Lehey wrote:
>> On Monday, 25 November 2002 at 15:42:37 +, Adam Laurie wrote:
>>
>>> hi,
>>>
>>> who is the best person to talk to regarding vinum docco?
Greg 'groggy' Lehey wrote:
On Monday, 25 November 2002 at 15:42:37 +, Adam Laurie wrote:
hi,
who is the best person to talk to regarding vinum docco?
I suppose I'm as good as any.
the reason i ask is because i recently had to recover a crashed
system with vinum runin
On Monday, 25 November 2002 at 15:42:37 +, Adam Laurie wrote:
> hi,
>
> who is the best person to talk to regarding vinum docco?
I suppose I'm as good as any.
> the reason i ask is because i recently had to recover a crashed
> system with vinum runinng on it, and i had
On Tuesday, 19 November 2002 at 9:05:19 -0500, Phillip Smith (3BAGSMEDIA) wrote:
>
> Hoping that the gods are with me and that you knowledgeable people can
> assist me with this _really_ big screw up...
>
> FreeBSD4.6-stable
>
> I was setting up Vinum (rather successfully I
Hoping that the gods are with me and that you knowledgeable people can
assist me with this _really_ big screw up...
FreeBSD4.6-stable
I was setting up Vinum (rather successfully I might add) until last when
I tried to configure a second mirror with two different drives...
All I can tell you is
On Tuesday, 5 November 2002 at 17:58:11 -0500, Frank Tobin wrote:
> Frank Tobin, on 2002-11-05, wrote:
>
>> I'm trying to recover as much data as possible from a vinum partition
>> that was on top of a faulty hd. To make sure vinum doesn't wipe
>> anything accid
Frank Tobin, on 2002-11-05, wrote:
> I'm trying to recover as much data as possible from a vinum partition
> that was on top of a faulty hd. To make sure vinum doesn't wipe
> anything accidentally, I'd like to get access to it as a normal fbsd
> partition or slice. I
1999, machine, I have a
vinum volume with two plexes, each with a single subdisk. (There are
other volumes, but they are 'okay' and probably not relevant). One of the
subdisks is on a hd with read errors.
The volume's name is 'data', and the subdisk data.p0.s0 is on is /de
I'm trying to recover as much data as possible from a vinum partition that
was on top of a faulty hd. To make sure vinum doesn't wipe anything
accidentally, I'd like to get access to it as a normal fbsd partition or
slice. Is it possible to tell dd to read the vinum partition, s
On Sunday, 27 October 2002 at 22:21:34 -0500, Tom Parquette wrote:
> I had something happen to my concatenated vinum drive.
> Looking at /var/log/messages I think it may be calling out a hardware
> problem on one of my drives.
>
> This configuration has been running for a wee
I had something happen to my concatenated vinum drive.
Looking at /var/log/messages I think it may be calling out a hardware
problem on one of my drives.
This configuration has been running for a week or so without complaining.
I call myself VERY green with vinum and I would appreciate someone
AM, Drew Tomlinson wrote:
>> On Sunday, October 20, 2002 5:52 PM, Drew Tomlinson wrote:
>>
>>> From what I've read, it appears that if I create a concatenated
>>> volume using vinum or ccd, I will destroy whatever data I already
>>> have on the disks. Is
gt;From what I've read, it appears that if I create a concatenated
> volume
> > using vinum or ccd, I will destroy whatever data I already have on
> the
> > disks. Is this correct? Is there anyway to do it without
> destroying
> > the data? I have one 80G archive drive an
October 2002 at 17:06:01 -0700, Drew Tomlinson wrote:
> > I'm sure the answer to my question is on the Net somewhere but after
a
> > day and a half of searching, I've decided to plea for help. :)
> >
> > The error I get when I attempt to create the volume is:
I've decided to plea for help. :)
>
> The error I get when I attempt to create the volume is:
>
> vinum -> create ftp_vinum.conf
>4: sd length 76319m drive ftp1
> ** 4 No space for on ftp1: No space left on device
>
> The disk, volume, and plex are creat
I'm sure the answer to my question is on the Net somewhere but after a
day and a half of searching, I've decided to plea for help. :)
The error I get when I attempt to create the volume is:
vinum -> create ftp_vinum.conf
4: sd length 76319m drive ftp1
** 4 No space for on f
it, but
wouldn't that work?
It sounds to me like he is talking about software raid.
Take a look at the 'vinum' stuff.
I just did this over the weekend for a client. Added a drive to an existing
vinum mirror set, and then used growfs to increase the filesystem size.
Worked grea
te a concatenated
>> volume using vinum or ccd, I will destroy whatever data I already
>> have on the disks. Is this correct? Is there anyway to do it
>> without destroying the data? I have one 80G archive drive and have
>> filled it. I added another and would like to have both
gt; It sounded like he was asking about growfs(8). I haven't used it, but
>> wouldn't that work?
>
> It sounds to me like he is talking about software raid.
> Take a look at the 'vinum' stuff.
That's what he's talking about.
> But, I don't thin
- Original Message -
From: "Drew Tomlinson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, October 20, 2002 5:52 PM
Subject: Vinum - A Way to Create Without Losing Data?
> >From what I've read, it appears that if I create a concatenated
vo
On Sunday, 20 October 2002 at 20:47:08 -0500, Kirk Strauser wrote:
>
> At 2002-10-21T01:15:48Z, "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>
>>> I have one 80G archive drive and have filled it. I added another and
>>> would like to have both drives seen by the system as one 160G drive.
>
>>
At 2002-10-21T01:15:48Z, "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> I have one 80G archive drive and have filled it. I added another and
>> would like to have both drives seen by the system as one 160G drive.
> You can't do that. UFS won't let you coalesce two file systems. Neither
On Sunday, 20 October 2002 at 17:52:52 -0700, Drew Tomlinson wrote:
>> From what I've read, it appears that if I create a concatenated volume
> using vinum or ccd, I will destroy whatever data I already have on the
> disks. Is this correct?
Sometimes.
> Is there any
>From what I've read, it appears that if I create a concatenated volume
using vinum or ccd, I will destroy whatever data I already have on the
disks. Is this correct? Is there anyway to do it without destroying
the data? I have one 80G archive drive and have filled it. I added
ano
Greg,
Thank you. I got it running and I was able to mount /dev/vinum/public
on /mnt. df -H shows 97Gig which is very close to what I was expecting.
Greg 'groggy' Lehey wrote:
There are no "-v values". -v says "be verbose".
Stupid user error #1.
I've s
nks to Greg and Tony for clearing up a couple of things.
> I just learned something about the boot process.
>
> Continuing:
> I recreated my error and this is what I got:
> vinum
> Vinum -> concat -n public -v /dev/ad5s1e /dev/ad6s1e /dev/ad7s1e
> volume public
> plex n
OK.
Thanks to Greg and Tony for clearing up a couple of things.
I just learned something about the boot process.
Continuing:
I recreated my error and this is what I got:
vinum
Vinum -> concat -n public -v /dev/ad5s1e /dev/ad6s1e /dev/ad7s1e
volume public
plex name public.p0 org concat
dr
Tom,
[EMAIL PROTECTED] said:
> At boot, I get the following:
> vinum: loaded
> vinum: /dev is mounted read-only not rebuilding /dev/vinum
> Can't open /dev/vinum/Control read only file system
I haven't looked at this on 4.7, but on the releases I'm working
on (4.2 a
On Thursday, 17 October 2002 at 20:53:41 -0400, Tom Parquette wrote:
> This is the first time I have tried to do anything with Vinum.
> This is on a 4.7-RELEASE machine.
> I'm doing a "minimal" installation over the Internet using the two
> floppy disk install met
This is the first time I have tried to do anything with Vinum.
This is on a 4.7-RELEASE machine.
I'm doing a "minimal" installation over the Internet using the two
floppy disk install method.
I have several IDE volumes that I am trying to concatenate.
After I complete the inst
On Wednesday, 9 October 2002 at 17:40:31 -0700, Jack Twilley wrote:
>>>>>> "Greg" == Greg Lehey writes:
>
>>> I had a bad experience this weekend with vinum, SCSI and new
>>> disks, and I'm not sure which part's at fault.
>
>>>>> "Greg" == Greg Lehey writes:
Jack> I had a bad experience this weekend with vinum, SCSI and new
Jack> disks, and I'm not sure which part's at fault.
Greg> Well, you're getting mulitple error messages from the SCSI
Greg> subsystem, a
On Tuesday, 8 October 2002 at 21:44:53 -0700, Jack Twilley wrote:
> I had a bad experience this weekend with vinum, SCSI and new disks,
> and I'm not sure which part's at fault.
Well, you're getting mulitple error messages from the SCSI subsystem,
and none from Vinum.
>
I had a bad experience this weekend with vinum, SCSI and new disks,
and I'm not sure which part's at fault. I installed ten new 4G disks,
built two striped plexes of five disks each, and mirrored them. Two
drives on the second plex generated pages of SCSI errors on the
console
On Thursday, 3 October 2002 at 17:00:36 +0100, Alasdair Lumsden wrote:
> Hello,
>
> I have a problem recovering a Vinum raid5 stripeset, and it was
> recommended that I post the problem here.
>
> ...
>
> I am at a loss for what to do next.
Take a look at the man page vin
Hello,
I have a problem recovering a Vinum raid5 stripeset, and it was
recommended that I post the problem here.
Basically, I created a Raid5 Stripeset:
drive ibm120ad2 device /dev/ad2s1e
drive ibm120ad5 device /dev/ad5s1e
drive ibm120ad7 device /dev/ad7s1e
volume raid5
plex org raid5
On Wednesday, 25 September 2002 at 9:48:22 +1000, Pietralla, Siegfried P wrote:
> hi all,
>
> i'm running 4.3 on partition ad0s3. i tried to install 4.6.2 on ad3s2 and
> when i booted back up on ad0s3 i lost my vinum partition which lives in
> ad3s4a ( i did not note down the
hi all,
i'm running 4.3 on partition ad0s3. i tried to install 4.6.2 on ad3s2 and
when i booted back up on ad0s3 i lost my vinum partition which lives in
ad3s4a ( i did not note down the error message :( so don't ask :) ). i did a
' dd if=/dev/ad3s4a | od -c ' and it looke
On Tuesday, 24 September 2002 at 10:49:34 -0400, Steve Shorter wrote:
> Howdy!
>
> I have 2 disks on separate SCSI busses that are
> striped to form a single vinum volume. They are recognized as
> da0 and da1
>
> I want to add 1 more disk to each SCSI buss and cre
Howdy!
I have 2 disks on separate SCSI busses that are
striped to form a single vinum volume. They are recognized as
da0 and da1
I want to add 1 more disk to each SCSI buss and create
another striped vinum volume, but keep the initial vinum volume
intact.
The issue
901 - 951 of 951 matches
Mail list logo
