linux-kernel - Re: XFS undeletable files. (3.11rc3)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130731061129.GA354@x4>
Date:	Wed, 31 Jul 2013 08:11:29 +0200
From:	Markus Trippelsdorf <markus@...ppelsdorf.de>
To:	Dave Jones <davej@...hat.com>, Dave Chinner <david@...morbit.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>, xfs@....sgi.com
Subject: Re: XFS undeletable files. (3.11rc3)

On 2013.07.30 at 16:26 -0400, Dave Jones wrote:
> On Thu, Jul 25, 2013 at 02:15:38PM +1000, Dave Chinner wrote:
>  > On Thu, Jul 11, 2013 at 10:39:30PM -0400, Dave Jones wrote:
>  > > Just saw this during boot after an unclean shutdown. It hung afterwards.
>  > > 
>  > > [   97.162665] XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file: fs/xfs/xfs_dir2_sf.c, line: 358
>  > > [   97.164646] ------------[ cut here ]------------
>  > 
>  > I just reproduced this by chance. I know exactly what I was doing
>  > when it went bang, so I might be able to reduce it from scattergun
>  > blast testing to be able to reproduce it on demand.
> 
> I xfs_repair'd that disk a week or so back, and have been fine until today when..
> 
> (16:22:57:root@...osum:tmp.6)# ll
> ls: cannot access : No such file or directory
> total 0
> ?????????? ? ? ? ?            ? ?
> (16:22:58:root@...osum:tmp.6)# cd ..
> (16:23:06:root@...osum:tmp)# rm -rf tmp.6
> rm: cannot remove ‘tmp.6’: Directory not empty
> (16:23:14:root@...osum:tmp)# cd -
> /home/davej/src/trinity/tmp/tmp.6
> (16:23:23:root@...osum:tmp.6)# stat *
> stat: cannot stat ‘\020’: No such file or directory
> 
> I don't know if this is residual crap from that first problem that never got fixed up,
> or something new.
> 
> Any ideas ?

If you have crashed your test machine running an rc1 or rc2 kernel, you
must run xfs_repair again to clean up possible corruption (that happened
during log replay). The fix (commit e1b4271ac26) is in rc3.

-- 
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/