SLAVE
> amd64
>
> This time, they're directories, not files. And they're cold, apart
> from find(1) and dump(8). Perhaps there's a one in a billion race with
> st_atime updates?
>
> Also:
>
> fsdb (inum: 62772027)> cd 85
> command `cd 85
> '
On Thu, Nov 19, 2015 at 08:31:13AM -0800, Brian Buhrow wrote:
> Hello. Have you ruled out a hardware problem? Also, are you running
> with WAPBL or just straight FFS?
Likely not hardware, unless it's in-memory corruption, since it's
raidframe raid-1 and I've previously diff'ed the mirrors
Hello. Have you ruled out a hardware problem? Also, are you running
with WAPBL or just straight FFS?
-thanks
-Brian
On Wed, Nov 26, 2014 at 09:37:22PM +1100, Paul Ripke wrote:
> On Tue, Nov 25, 2014 at 08:42:29AM -0500, Christos Zoulas wrote:
> > On Nov 25, 1:22pm, s...@stix.id.au (Paul Ripke) wrote:
> > -- Subject: Re: Unallocated inode
> >
> > | On Mon, Nov 24, 2014 at 08:01:
On Wed, Nov 26, 2014 at 01:51:57PM +1100, Paul Ripke wrote:
> On Tue, Nov 25, 2014 at 09:25:02AM +0100, Martin Husemann wrote:
> > On Tue, Nov 25, 2014 at 01:22:00PM +1100, Paul Ripke wrote:
> > > slave:ksh$ find /home/tmp > /dev/null
> > > find: /home/tmp/badfile: Bad file descriptor
> >
> > Is t
EF> Is there an mpt(4) controller involved? If yes, did you get any timeouts on
it?
PR> Nope, no mpt(4). All boring directly connected SATA thru ahcisatai(4).
PR> However, I notice upon closer inspection, I did get a SATA timeout the
PR> night the corruption was noticed:
PR>
PR> Nov 23 03:47:10
On Tue, Nov 25, 2014 at 08:42:29AM -0500, Christos Zoulas wrote:
> On Nov 25, 1:22pm, s...@stix.id.au (Paul Ripke) wrote:
> -- Subject: Re: Unallocated inode
>
> | On Mon, Nov 24, 2014 at 08:01:57PM -0500, Christos Zoulas wrote:
> | > On Nov 25, 10:59am, s...@stix.id.au
On Wed, Nov 26, 2014 at 02:18:12PM +1100, Paul Ripke wrote:
> On Tue, Nov 25, 2014 at 12:00:48PM +0100, Edgar Fu? wrote:
> > > Nope, it's inaccessible - again, it was the daily security reports
> > > that alerted me:
> > >
> > > slave:ksh$ find /home/tmp > /dev/null
> > > find: /home/tmp/badfile:
On Tue, Nov 25, 2014 at 09:25:02AM +0100, Martin Husemann wrote:
> On Tue, Nov 25, 2014 at 01:22:00PM +1100, Paul Ripke wrote:
> > slave:ksh$ find /home/tmp > /dev/null
> > find: /home/tmp/badfile: Bad file descriptor
>
> Is that FS on raidframe?
>
> I saw something like this once and blamed it o
On Tue, Nov 25, 2014 at 12:00:48PM +0100, Edgar Fu? wrote:
> > Nope, it's inaccessible - again, it was the daily security reports
> > that alerted me:
> >
> > slave:ksh$ find /home/tmp > /dev/null
> > find: /home/tmp/badfile: Bad file descriptor
> I remember having run into the same thing.
> I sim
On Nov 25, 1:22pm, s...@stix.id.au (Paul Ripke) wrote:
-- Subject: Re: Unallocated inode
| On Mon, Nov 24, 2014 at 08:01:57PM -0500, Christos Zoulas wrote:
| > On Nov 25, 10:59am, s...@stix.id.au (Paul Ripke) wrote:
| > -- Subject: Re: Unallocated inode
| >
| > | On Tue, Sep 02, 2
> Nope, it's inaccessible - again, it was the daily security reports
> that alerted me:
>
> slave:ksh$ find /home/tmp > /dev/null
> find: /home/tmp/badfile: Bad file descriptor
I remember having run into the same thing.
I simultaneously had another FS problem (the kernel repeatedly panic()ing
on
On Tue, Nov 25, 2014 at 01:22:00PM +1100, Paul Ripke wrote:
> slave:ksh$ find /home/tmp > /dev/null
> find: /home/tmp/badfile: Bad file descriptor
Is that FS on raidframe?
I saw something like this once and blamed it on a failing disk (which
did show SMART errors shortly afterwards), i.e. I assum
On Mon, Nov 24, 2014 at 08:01:57PM -0500, Christos Zoulas wrote:
> On Nov 25, 10:59am, s...@stix.id.au (Paul Ripke) wrote:
> -- Subject: Re: Unallocated inode
>
> | On Tue, Sep 02, 2014 at 06:15:49PM -0400, Christos Zoulas wrote:
> | > On Sep 2, 2:27pm, s...@stix.id.au
On Tue, Sep 02, 2014 at 06:15:49PM -0400, Christos Zoulas wrote:
> On Sep 2, 2:27pm, s...@stix.id.au (Paul Ripke) wrote:
> -- Subject: Re: Unallocated inode
>
> | Yeah, that's what scares me - it was the daily rsync and security cron
> | jobs starting to generate errors tha
On Nov 25, 10:59am, s...@stix.id.au (Paul Ripke) wrote:
-- Subject: Re: Unallocated inode
| On Tue, Sep 02, 2014 at 06:15:49PM -0400, Christos Zoulas wrote:
| > On Sep 2, 2:27pm, s...@stix.id.au (Paul Ripke) wrote:
| > -- Subject: Re: Unallocated inode
| >
| > | Yeah, that's wh
On Sep 2, 2:27pm, s...@stix.id.au (Paul Ripke) wrote:
-- Subject: Re: Unallocated inode
| Yeah, that's what scares me - it was the daily rsync and security cron
| jobs starting to generate errors that alerted me - those inodes must've
| been marked partially allocated only recently
On Mon, Sep 01, 2014 at 03:01:01AM -0400, Christos Zoulas wrote:
> On Sep 1, 2:54pm, s...@stix.id.au (Paul Ripke) wrote:
> -- Subject: Re: Unallocated inode
>
> | Running a second fsck pass comes up clean. What surprises me is that my
> | machine has been up ~100 days... I
On Sep 1, 2:54pm, s...@stix.id.au (Paul Ripke) wrote:
-- Subject: Re: Unallocated inode
| Running a second fsck pass comes up clean. What surprises me is that my
| machine has been up ~100 days... I find it hard to believe that a power
| loss or similar unclean shutdown would generate filesystem
t; slave:ksh$ sudo find /home -xdev -ls > /dev/null
>> find: /home/netbsd/cvsroot/pkgsrc/japanese/p5-Jcode/pkg/Attic/PLIST,v: Bad
>> file descriptor
>> find:
>> /home/netbsd/cvsroot/pkgsrc/print/texlive-pdftools/patches/Attic/patch-ac,v:
>> Bad file descriptor
>&g
On Aug 29, 12:33pm, Edgar =?iso-8859-1?B?RnXf?= wrote:
} Subject: Re: Unallocated inode
} Btw.: Has anyone tried to import my mpt(4) enhancements? I had several
} crashes of the disc firmware / controller hick-ups that were caught by
} my patch (I later updated the firmware and had no crashes
> Hello. If the patches you're talking about are the ones we worked on
> for the mpt(4) driver, they were committed around February of this year.
Ah, thanks. I'll have a look at what you committed.
> does anyone have any idea what might be causing them?
> This appears similar to issues reported previously:
> http://mail-index.netbsd.org/tech-kern/2013/10/19/msg015770.html
In my case, they were most probably caused by the disc firmware crashing,
the MPT SAS controller locking up and mpt(4) no
ese/p5-Jcode/pkg/Attic/PLIST,v:
>Bad file descriptor
>find:
>/home/netbsd/cvsroot/pkgsrc/print/texlive-pdftools/patches/Attic/patch-ac,v:
>Bad file descriptor
>
>fsdb tells me they're "unallocated inode"s, which I can easily fix,
>but does anyone have any idea what
panese/p5-Jcode/pkg/Attic/PLIST,v: Bad
> file descriptor
> find:
> /home/netbsd/cvsroot/pkgsrc/print/texlive-pdftools/patches/Attic/patch-ac,v:
> Bad file descriptor
>
> fsdb tells me they're "unallocated inode"s, which I can easily fix,
> but does anyone have any ide
ic/patch-ac,v:
Bad file descriptor
fsdb tells me they're "unallocated inode"s, which I can easily fix,
but does anyone have any idea what might be causing them? This
appears similar to issues reported previously:
http://mail-index.netbsd.org/tech-kern/2013/10/19/msg015770.html
26 matches
Mail list logo
