NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/50707: rm: fts_read: No such file or directory
The following reply was made to PR kern/50707; it has been noted by GNATS.
From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand%systella.fr@localhost>
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
netbsd-bugs%netbsd.org@localhost,
"NetBSD Users's Discussion List" <netbsd-users%NetBSD.org@localhost>
Cc:
Subject: Re: kern/50707: rm: fts_read: No such file or directory
Date: Fri, 5 Aug 2016 09:14:28 +0200
BERTRAND Joël a écrit :
> The following reply was made to PR kern/50707; it has been noted by GNATS.
>
> From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand%systella.fr@localhost>
> To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
> netbsd-bugs%netbsd.org@localhost
> Cc:
> Subject: Re: kern/50707: rm: fts_read: No such file or directory
> Date: Tue, 5 Jul 2016 09:59:25 +0200
>
> BERTRAND Joël a écrit :
> > The following reply was made to PR kern/50707; it has been noted by GNATS.
> >
> > From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand%systella.fr@localhost>
> > To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
> > netbsd-bugs%netbsd.org@localhost
> > Cc:
> > Subject: Re: kern/50707: rm: fts_read: No such file or directory
> > Date: Mon, 27 Jun 2016 09:10:28 +0200
> >
> > Some news.
> >
> > Last saturday, I have tried to bissect fts code without any success,
> > but I have seen that disk corruption only occurs on high disk I/O (for
> > example make clean in ports tree, I use MAKE_JOBS=8 as this server
> > contains an i7 CPU with 8 threads). All disk corruptions are directories
> > without '.'. fsck returns that directories were 'half allocated'.
> >
> > Best regards,
> >
> > JKB
> >
> >
>
> Hello,
>
> Another one, but without any 'rm'. This morning, I have received a mail
> from Charlie root :
>
> daily insecurity output for Tue Jul 5 03:15:01 CEST 2016
> Checking setuid files and devices:
> Setuid/device find errors:
> find: fts_read: No such file or directory
>
> I wonder if this issue could be related to disk internal cache
> strategy. Now, both disks return :
> legendre# legendre# dkctl /dev/wd1 getcache
> /dev/wd1d: read cache enabled
> /dev/wd1d: write-back cache enabled
> /dev/wd1d: read cache enable is not changeable
> /dev/wd1d: write cache enable is changeable
> /dev/wd1d: cache parameters are not savable
> legendre# dkctl /dev/wd0 getcache
> /dev/wd0d: read cache enabled
> /dev/wd0d: write-back cache enabled
> /dev/wd0d: read cache enable is not changeable
> /dev/wd0d: write cache enable is changeable
> /dev/wd0d: cache parameters are not savable
> legendre#
>
> Is there a hope to fix this particularly bad issue ?
>
> Best regards,
>
> JKB
>
>
Hello,
Some news. Last night, kernel panics with :
/: bad dir ino 2130825 at offset 0: mangled entry
panic: bad dir
cpu5: Begin traceback...
vpanic() at netbsd:vpanic+0x13c
snprintf() at netbsd:snprintf
ufs_dirbadentry() at netbsd:ufs_dirbadentry
ufs_lookup() at netbsd:ufs_lookup+0x4c3
VOP_LOOKUP() at netbsd:VOP_LOOKUP+0x34
lookup_once() at netbsd:lookup_once+0x18b
namei_tryemulroot() at netbsd:namei_tryemulroot+0x612
namei() at netbsd:namei+0x43
fd_nameiat.isra.0() at netbsd:fd_nameiat.isra.0+0x54
do_sys_statat() at netbsd:do_sys_statat+0x72
sys___lstat50() at netbsd:sys___lstat50+0x25
syscall() at netbsd:syscall+0x9a
--- syscall (number 441) ---
7f7ff70a705a:
cpu5: End traceback...
uvm_fault(0xfffffe83b899b760, 0x0, 2) -> e
uvm_fault(0xfffffe840f88e310, 0x0, 2) -> e
fatal page fault in supervisor mode
fatal page fault in supervisotrr ampo dtey
pe 6 code 2 rip ffffffff805db5b9 cs 8 rflags 10202 cr2 84 ilevel 8 rsp
fffffe812108fb98
trap type 6 code 2 rip ffffffff805db5b9 cs 8 rflags 10202 cr2 84 ilevel
8 rsp ffcfufrflew8p1 2102xf3f4fbfaf8e
83ea9c8200 pid 20893.3 lowest kstack 0xfffffe812108d2c0
dumping to dev 18,1 (offset=251903, size=4162816):
curlwp 0xfffffe83dcdc6440 pid 2611.7 lowest kstack 0xfffffe81212322c0
I suppose this panic is related to tfs error I have seen. I'm pretty
sure that this server doesn't have harware issue (disks smart parameters
are corrects and I have checked these disks in another workstation).
For information, boths disks are :
Device Model: TOSHIBA DT01ACA100
Regards,
JKB
Home |
Main Index |
Thread Index |
Old Index