Date: Wed, 9 Jun 1999 21:51:27 +0200 From: "John Andersson" <yottaman@writeme.com> To: <freebsd-hackers@freebsd.org> Subject: Re: Bad sectors on vinum volym Message-ID: <006001beb2b1$763d0aa0$09a52fc2@bugsoft.hik.se> References: <003901beb279$92b169c0$0fad2fc2@te.hik.se> <19990609205956.B57243@cicely8.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your response, you are probably right. I created the vinum volym under the 3.1 release (or it may have been the 3.0 release) and I maximized the partition size to the last block with trial and error. When checking the sector number returned by fsck (44609178, ...), it seems to be exactly at the end of the partition size (4460918k per subdrive), altough I have not done the math completly, there seems to be some relation. It would be very interesting to try to use your tool to decrease the filesystem size (or the subdrive size in the plex?). Does it work with vinum too? Either way, this is good news, since there problably does not exists any bad sectors, just some error in the partition size calculation and a complete reconstruction of the vinum volym would fix all problem (hopefully... ;-). /John ----- Original Message ----- From: Bernd Walter <ticso@cicely.de> To: John Andersson <yottaman@writeme.com> Sent: Wednesday, June 09, 1999 8:59 PM Subject: Re: Bad sectors on vinum volym > On Wed, Jun 09, 1999 at 03:11:23PM +0200, John Andersson wrote: > > I seem to have some bad sectors on my vinum volume, fsck reports the > > following and does not seem to be able to fix it: > > THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 44609178, 44609179, > > > > ***** FILE SYSTEM STILL DIRTY ***** > > ***** FILE SYSTEM WAS MODIFIED ***** > > ***** PLEASE RERUN FSCK ***** > > > > This was just a cut of the fsck output, it totally reports about 10 sectors > > that it can't read or write to. > > I tried to execute the badsect program (badsect /xxx/BAD 44609178 44609179), > > but it reports: > > Cannot find dev 061004206 corresponding to /xxx/BAD > > > > The volym in question consists of a 5 disc striped plex. > > Is it possible to run badsect on a vinum volym to fix this? > > I would prefer not to lose all data on the volym, and since it's about 40G > > of data I can't backup all data. > > I run FreeBSD 3.2-Release. > > It is possible to force a mount and continue to use the volym, but some > > directories are unaccessible. > > > Maybe there is a way to recover the partition without the need to restore > the data (backup would be still a good idea). > If it's the old sizeproblem it should be possible with the new volumesize to > which the recent vinum corrected the partition to use a tool I've written > during the last weeks. > > The tool is build to increase a filesystem after the partition it is on > was increased too. > It should be possible to decrease the filesystem so it won't refer to the > unavailable sectors anymore. > A fsck run after that should remove all references (files, ...) to these > blocks. > My tools still has some bugs - but the won't appear when decreasing the fs. > > -- > B.Walter COSMO-Project http://www.cosmo-project.de > ticso@cicely.de info@cosmo-project.de > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006001beb2b1$763d0aa0$09a52fc2>