Date: Tue, 9 Apr 2002 14:23:47 +0000 (GMT) From: Kris Kirby <kris@catonic.net> To: Greg 'groggy' Lehey <grog@FreeBSD.org> Cc: <freebsd-questions@freebsd.org> Subject: Re: Vinum, "stale" disk. Message-ID: <Pine.BSF.4.33.0204091419160.14726-100000@spaz.catonic.net> In-Reply-To: <20020322141126.O463@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 22 Mar 2002, Greg 'groggy' Lehey wrote: > The thread claims that RAID-5 plexes are corrupted if you revive them > while they're mounted. You'd be safer to unmount the file system > first. I tried, but with a bozo'd drive, I had to kick the machine. Not Smart, I know. I've found the root cause now -- ad3 decided it no longer wished to be with me, leaving me in a very uncomfortable position. .s0 is up, and reliable, .s1 is stale -- but I have reason to believe that no writes were made to the disk during the time I attempted to access it, just a simple tar job and that was about it. It is very rather important that I recover this data, however. .s3 is the crashed (really!) disk. This was a RAID5 system, with each subdisk on a seperate disk. How can I "force" .s1 up from stale? How badly will I trash the FS on s1? -- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. <kris@nospam.catonic.net> | IM: KrisBSD | HSV, AL. ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0204091419160.14726-100000>