NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/54935: dir corruption not fixed by fsck
The following reply was made to PR bin/54935; it has been noted by GNATS.
From: Christos Zoulas <christos%zoulas.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: bin/54935: dir corruption not fixed by fsck
Date: Tue, 4 Feb 2020 17:28:22 -0500
clri/fsdb is your friend. do you have a copy
of it?
christos
> On Feb 4, 2020, at 1:50 PM, "martin%netbsd.org@localhost" <martin%netbsd.org@localhost wrote:
>=20
> =EF=BB=BF
>>=20
>> Number: 54935
>> Category: bin
>> Synopsis: dir corruption not fixed by fsck
>> Confidential: no
>> Severity: critical
>> Priority: high
>> Responsible: bin-bug-people
>> State: open
>> Class: sw-bug
>> Submitter-Id: net
>> Arrival-Date: Tue Feb 04 18:50:00 +0000 2020
>> Originator: Martin Husemann
>> Release: NetBSD 9.99.45
>> Organization:
> The NetBSD Foundation, Inc.
>> Environment:
> System: NetBSD seven-days-to-the-wolves.aprisoft.de 9.99.45 NetBSD 9.99.45=
(GENERIC) #348: Mon Feb 3 08:14:54 CET 2020 martin@seven-days-to-the-wolves=
.aprisoft.de:/work/src/sys/arch/amd64/compile/GENERIC amd64
> Architecture: x86_64
> Machine: amd64
>> Description:
>=20
> I have a machine (running -current as of today) wich apparently has a slig=
thly
> corrupted filesystem.
>=20
> I booted single user and ran fsck -fy /
>=20
> That finished and claimed to have fixed the fs.
>=20
> On reboot I got:
> [ 3489.8572502] /: bad dir ino 1054908 at offset 8120: Bad dir (not rounde=
d), reclen=3D0x803, namlen=3D116, dirsiz=3D128 <=3D reclen=3D2051 <=3D maxsi=
ze=3D72, flags=3D0x5001, entryoffsetinblock=3D8120, dirblksiz=3D512
>=20
> and on next boot:
>=20
> [ 17.5679221] /: bad dir ino 2107008 at offset 8128: NUL in name [raic] i=
=3D4, namlen=3D6
> [ 27.9025333] panic: /: bad dir ino 1077399 at offset 8112: NUL in name [=
libdc++.a] i=3D9, namlen=3D11
>=20
> Backup and restore time - but somehow I guess fsck_ffs should have dealt w=
ith
> it properly.
>=20
>> How-To-Repeat:
> n/a
>=20
>> Fix:
> n/a
Home |
Main Index |
Thread Index |
Old Index