Date: Tue, 9 Dec 2003 00:05:34 +0200 From: Ion-Mihai Tetcu <itetcu@apropo.ro> To: Doug White <dwhite@gumbysoft.com> Cc: freebsd-current@freebsd.org Subject: Re: (a new fsdb dump) Re: fsck sig 11 (cannot alloc 4216257920bytes for inoinfo) Message-ID: <20031209000534.35a4b474.itetcu@apropo.ro> In-Reply-To: <20031208124541.W15361@carver.gumbysoft.com> References: <20031208181611.1a358bb5.itetcu@apropo.ro> <20031208202837.4a05d06a.itetcu@apropo.ro> <20031208124541.W15361@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 8 Dec 2003 12:47:27 -0800 (PST) Doug White <dwhite@gumbysoft.com> wrote: > On Mon, 8 Dec 2003, Ion-Mihai Tetcu wrote: > > > Here is a fsdb dump on the previous and next inode, hoepe it serves > > at something. THE FOLLOWING DISK SECTORS COULD NOT BE READ means bad > > hardware ? It would be strange as the HDD is 6 month old and smart > > doeasn't report anything. > > The block numbers are impossibly large. It appears you have a fatal > level of disk and filesystem corruption. I would suggest pulling down > the Seagate test tools and running a scan on your disk, then newfs & > reinstall. I've did the test by moving the HDD to a winXP computer and running the DiscWizard Online's test all but the most compprehensing one (reading all the sectors) and all is reported to be OK; I'll do the last one to. > I don't know about you, but I don't have files this large: > > 11,126,052,392,626,458,067 Whish I could :) thanks, IOnut -- IOnut Unregistered ;) FreeBSD user
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031209000534.35a4b474.itetcu>