Re: Mangled file system directory panic

2016-08-12 Thread Christos Zoulas
On Aug 12, 6:51pm, ja...@uninett.no (Jarle Greipsland) wrote: -- Subject: Re: Mangled file system directory panic | chris...@astron.com (Christos Zoulas) writes: | > In article <20160811.153708.78150616.ja...@uninett.no>, | > Jarle Greipsland wrote: | >>> The panic messa

Re: Mangled file system directory panic

2016-08-12 Thread Jarle Greipsland
chris...@astron.com (Christos Zoulas) writes: > In article <20160811.153708.78150616.ja...@uninett.no>, > Jarle Greipsland wrote: >>> The panic messages reported by crash is something like: >>> System panicked: /mnt: bad dir ino 42369 at offset 560: NUL in name [] >>i=0, namlen=4 [ ... ] >>I have

Re: Mangled file system directory panic

2016-08-12 Thread Jarle Greipsland
co...@sdf.org writes: > On Thu, Aug 11, 2016 at 03:37:08PM +0200, Jarle Greipsland wrote: >> [ Followups to port-i386, please ] >> I wrote[1]: >> > I have a system where I can almost deterministally provoke a >> > kernel panic by doing a 'tar -zxpf comp.tgz'. >> > >> > The panic messages reported

Re: Mangled file system directory panic

2016-08-11 Thread Christos Zoulas
In article <20160811.153708.78150616.ja...@uninett.no>, Jarle Greipsland wrote: >[ Followups to port-i386, please ] >I wrote[1]: >> I have a system where I can almost deterministally provoke a >> kernel panic by doing a 'tar -zxpf comp.tgz'. >> >> The panic messages reported by crash is somethin

Re: Mangled file system directory panic

2016-08-11 Thread coypu
On Thu, Aug 11, 2016 at 03:37:08PM +0200, Jarle Greipsland wrote: > [ Followups to port-i386, please ] > I wrote[1]: > > I have a system where I can almost deterministally provoke a > > kernel panic by doing a 'tar -zxpf comp.tgz'. > > > > The panic messages reported by crash is something like: >

Re: Mangled file system directory panic

2016-08-11 Thread Jarle Greipsland
[ Followups to port-i386, please ] I wrote[1]: > I have a system where I can almost deterministally provoke a > kernel panic by doing a 'tar -zxpf comp.tgz'. > > The panic messages reported by crash is something like: > System panicked: /mnt: bad dir ino 42369 at offset 560: NUL in name [] i=0, >

Mangled file system directory panic

2016-07-30 Thread Jarle Greipsland
Hi, I have a system where I can almost deterministally provoke a kernel panic by doing a 'tar -zxpf comp.tgz'. The panic messages reported by crash is something like: System panicked: /mnt: bad dir ino 42369 at offset 560: NUL in name [] i=0, namlen=4 The directory mangling is quite severe, so