re: Fixing vinum after removing a HDD
Date: Thu, 16 Dec 2004 21:56:29 -0800 (PST) From: orville weyrich [EMAIL PROTECTED] Subject: re: Fixing vinum after removing a HDD To: [EMAIL PROTECTED] On Wed, 2004-02-11 at 17:02, Greg 'groggy' Lehey wrote: resetconfig The resetconfig command completely obliterates the vinum configu- ration on a system. Use this command only when you want to com- pletely delete the configuration. I'm completely baffled that people want to use this command so much. The correct sequence is to remove the drive, replace it with something else with a Vinum partition, and then start the defective objects. It depends on the volume structures as to whether the data can still be recovered. PLEASE PLEASE PLEASE elaborate on what volume structuers CAN be recovered after resetconfig and what strucuters cannot. I am trying to deal with *invalid* drives in dumpconfig and not getting any answers. Thanks __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail __ Do you Yahoo!? Dress up your holiday email, Hollywood style. Learn more. http://celebrity.mail.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing vinum after removing a HDD
On Wednesday, 11 February 2004 at 19:30:52 -0800, Micheas Herman wrote: On Wed, 2004-02-11 at 17:02, Greg 'groggy' Lehey wrote: On Wednesday, 4 February 2004 at 19:52:03 +0100, Stijn Hoop wrote: On Wed, Feb 04, 2004 at 07:41:48PM +0100, [EMAIL PROTECTED] wrote: I'm running FreeBSD 4.8 on a system with 5 HDD's. ad0 is to be removed from the system. ad1, ad2 and ad3 contain my vinum drives. FreeBSD resides on the last disk (da0). Can anyone tell me if the following procedure is the right way to do it? 1. physically remove ad0 2. vinum resetconfig 3. change drivenumbers in vinum.conf 4. run vinum with the new configfile As far as my (limited) vinum knowledge goes, you really don't need to do a resetconfig. Correct. From the man page: resetconfig The resetconfig command completely obliterates the vinum configu- ration on a system. Use this command only when you want to com- pletely delete the configuration. I'm completely baffled that people want to use this command so much. The correct sequence is to remove the drive, replace it with something else with a Vinum partition, and then start the defective objects. Just a guess (arm chair psychology of users), but I suspect it is because they are thinking that they need to re-setup their drive. Maybe deleteconfig would be a more self documenting flag. Hmm, maybe. I'll think about this. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Re: Fixing vinum after removing a HDD
On Wednesday, 4 February 2004 at 19:52:03 +0100, Stijn Hoop wrote: On Wed, Feb 04, 2004 at 07:41:48PM +0100, [EMAIL PROTECTED] wrote: I'm running FreeBSD 4.8 on a system with 5 HDD's. ad0 is to be removed from the system. ad1, ad2 and ad3 contain my vinum drives. FreeBSD resides on the last disk (da0). Can anyone tell me if the following procedure is the right way to do it? 1. physically remove ad0 2. vinum resetconfig 3. change drivenumbers in vinum.conf 4. run vinum with the new configfile As far as my (limited) vinum knowledge goes, you really don't need to do a resetconfig. Correct. From the man page: resetconfig The resetconfig command completely obliterates the vinum configu- ration on a system. Use this command only when you want to com- pletely delete the configuration. I'm completely baffled that people want to use this command so much. The correct sequence is to remove the drive, replace it with something else with a Vinum partition, and then start the defective objects. It depends on the volume structures as to whether the data can still be recovered. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Re: Fixing vinum after removing a HDD
On Wed, 2004-02-11 at 17:02, Greg 'groggy' Lehey wrote: On Wednesday, 4 February 2004 at 19:52:03 +0100, Stijn Hoop wrote: On Wed, Feb 04, 2004 at 07:41:48PM +0100, [EMAIL PROTECTED] wrote: I'm running FreeBSD 4.8 on a system with 5 HDD's. ad0 is to be removed from the system. ad1, ad2 and ad3 contain my vinum drives. FreeBSD resides on the last disk (da0). Can anyone tell me if the following procedure is the right way to do it? 1. physically remove ad0 2. vinum resetconfig 3. change drivenumbers in vinum.conf 4. run vinum with the new configfile As far as my (limited) vinum knowledge goes, you really don't need to do a resetconfig. Correct. From the man page: resetconfig The resetconfig command completely obliterates the vinum configu- ration on a system. Use this command only when you want to com- pletely delete the configuration. I'm completely baffled that people want to use this command so much. The correct sequence is to remove the drive, replace it with something else with a Vinum partition, and then start the defective objects. Just a guess (arm chair psychology of users), but I suspect it is because they are thinking that they need to re-setup their drive. Maybe deleteconfig would be a more self documenting flag. Micheas It depends on the volume structures as to whether the data can still be recovered. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. -- Micheas Herman email: [EMAIL PROTECTED] Free Print Shop web: http://www.FreePrintShop.org phone: (415)648-3222fax: (415)648-4466 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fixing vinum after removing a HDD
Dear all, I'm running FreeBSD 4.8 on a system with 5 HDD's. ad0 is to be removed from the system. ad1, ad2 and ad3 contain my vinum drives. FreeBSD resides on the last disk (da0). Can anyone tell me if the following procedure is the right way to do it? 1. physically remove ad0 2. vinum resetconfig 3. change drivenumbers in vinum.conf 4. run vinum with the new configfile Thanks, Marc Disks currently in the system: ad0 (unused disk, to be removed from the system) ad1 Maxtor 6Y080L0 (contains 1st vinum subdisk) ad2 Maxtor 6Y080L0 (contains 2nd vinum subdisk) ad3 Maxtor 6Y080L0 (contains 3rd vinum subdisk) da0 QUANTUM ATLAS10K2-TY092L DDD6(contains all system partitions) My current vinum.conf: drive a device /dev/ad1s1h drive b device /dev/ad2s1h drive c device /dev/ad3s1h volume BigDisk0 plex org concat sd length 78159m drive a sd length 78159m drive b sd length 78159m drive c Disks after removing the 1st disk ad0 Maxtor 6Y080L0 (contains 1st vinum subdisk) ad1 Maxtor 6Y080L0 (contains 2nd vinum subdisk) ad2 Maxtor 6Y080L0 (contains 3rd vinum subdisk) da0 QUANTUM ATLAS10K2-TY092L DDD6(contains all system partitions) My future vinum.conf drive a device /dev/ad0s1h drive b device /dev/ad1s1h drive c device /dev/ad2s1h volume BigDisk0 plex org concat sd length 78159m drive a sd length 78159m drive b sd length 78159m drive c ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing vinum after removing a HDD
On Wed, Feb 04, 2004 at 07:41:48PM +0100, [EMAIL PROTECTED] wrote: I'm running FreeBSD 4.8 on a system with 5 HDD's. ad0 is to be removed from the system. ad1, ad2 and ad3 contain my vinum drives. FreeBSD resides on the last disk (da0). Can anyone tell me if the following procedure is the right way to do it? 1. physically remove ad0 2. vinum resetconfig 3. change drivenumbers in vinum.conf 4. run vinum with the new configfile As far as my (limited) vinum knowledge goes, you really don't need to do a resetconfig. Vinum writes the configuration to the disk and reads the information from it. I think it will be able to cope with a missing disk by itself because the label on it has not changed; on what is now /dev/ad1s1h vinum has stored the fact that this vinum drive is labeled 'a', and even if the freebsd device node changes names, vinum will still know that the then /dev/ad0s1h is labeled 'a'. Unfortunately this is only my understanding and I haven't yet needed to do such an operation for real. YMMV. --Stijn -- The right half of the brain controls the left half of the body. This means that only left handed people are in their right mind. pgp0.pgp Description: PGP signature
