g...@lexort.com (Greg Troxel) writes:
>As to how to find which file the block is in, there were programs ncheck
>and icheck in the old days (sixth and seventh edition sometime). It
>looks like fsdb will do this.
fsdb lets you find the inode that owns a disk block. You can use find
to search the
On Tue, Sep 05, 2017 at 06:05:08PM +, Steve Blinkhorn wrote:
> Is there a way of identifying the file that's affected from the fsbn?
> Because it's the boot partition and the server is far away I need to
> be sure the machine will come up in multi-user mode if I have to
> reboot.
>
I have fou
On Tue, Sep 05, 2017 at 06:05:08PM +, Steve Blinkhorn wrote:
> Is there a way of identifying the file that's affected from the fsbn?
> Because it's the boot partition and the server is far away I need to
> be sure the machine will come up in multi-user mode if I have to
> reboot.
pkgsrc/sysu
On Tue, Sep 05, 2017 at 06:05:08PM +, Steve Blinkhorn wrote:
> Is there a way of identifying the file that's affected from the fsbn?
> Because it's the boot partition and the server is far away I need to
> be sure the machine will come up in multi-user mode if I have to
> reboot.
I would absol
st...@prd.co.uk (Steve Blinkhorn) writes:
> Sep 5 16:56:49 trafalgar /netbsd: wd0a: error reading fsbn 1005056 of
> 1005056-1005087 (wd0 bn 1005119; cn 997 tn 2 sn 17), retrying
> Sep 5 16:56:49 trafalgar /netbsd: wd0: (uncorrectable data error)
>
> The fsbn is mostly 1005056 but sometimes 100
On Tue, Sep 05, 2017 at 08:30:51PM +0200, tlaro...@polynum.com wrote:
> FWIW, when I first saw this on a drive, NetBSD was able to recover and
> let me back-up the data (indeed very first thing to do). After, the
> SMART status was almost useless, since the faults reappeared until the
> disk finall
On Tue, Sep 05, 2017 at 06:19:31PM +, Steve Blinkhorn wrote:
> SMART supported, SMART enabled
> id value thresh crit collect reliability description raw
[..]
> 5 97 36 yes online positiveReallocated sector count 145
I would take this alone as a strong hint and go with Jukka's rec
On Tue, Sep 05, 2017 at 06:05:08PM +, Steve Blinkhorn wrote:
> Is there a way of identifying the file that's affected from the fsbn?
> Because it's the boot partition and the server is far away I need to
> be sure the machine will come up in multi-user mode if I have to
> reboot.
I think fsdb(
On Tue, Sep 05, 2017 at 07:44:59PM +0200, Martin Husemann wrote:
> On Tue, Sep 05, 2017 at 05:35:07PM +, Steve Blinkhorn wrote:
> > I have discovered a problem on a live server (i386) I run - this
> > is filling up /var/log/messages so that it has turned over more than
> > 10 times today.
> >
Is there a way of identifying the file that's affected from the fsbn?
Because it's the boot partition and the server is far away I need to
be sure the machine will come up in multi-user mode if I have to
reboot.
--
Steve Blinkhorn
You wrote:
>
> On Tue, Sep 05, 2017 at 05:35:07PM +, Steve B
On this server:
# atactl wd0 smart status
SMART supported, SMART enabled
id value thresh crit collect reliability description raw
1 446 yes online positiveRaw read error rate 221273574
3 980 yes online positiveSpin-up time0
4 100 20 no onlin
On Tue, Sep 05, 2017 at 05:35:07PM +, Steve Blinkhorn wrote:
> I have discovered a problem on a live server (i386) I run - this
> is filling up /var/log/messages so that it has turned over more than
> 10 times today.
>
> The message:
>
> Sep 5 16:56:49 trafalgar /netbsd: wd0a: error reading
I have discovered a problem on a live server (i386) I run - this
is filling up /var/log/messages so that it has turned over more than
10 times today.
The message:
Sep 5 16:56:49 trafalgar /netbsd: wd0a: error reading fsbn 1005056 of
1005056-1005087 (wd0 bn 1005119; cn 997 tn 2 sn 17), retrying
13 matches
Mail list logo
