On 4:27:49 pm 03/25/05 "Jason Munro" <[email protected]> wrote:
> On 4:06:54 pm 03/25/05 Andrew Morton <[email protected]> wrote:
> >
> > (Please dont' edit the cc line. Just do reply-to-all)
>
> Oops, reply-to-all it is.
>
> > "Jason Munro" <[email protected]> wrote:
> > >
> > > > [ 146.301026] rock: directory entry would overflow storage
> > > > [ 146.301044] rock: sig=0x5245, size=8, remaining=0
> > > > [ 158.388397] rock: directory entry would overflow storage
> > > > [ 158.388415] rock: sig=0x5850, size=36, remaining=34
> > > > [root@spc1 steven]#
> > >
> > >
> > > Same results with mm3 here, though mm2 will not boot on my
> > > machine so I'm not sure about that. 2.6.12-rc1 works fine,
> > > rc1-mm3 successfully mounts the cdrom device but shows no
> > > contents. Releveant dmsesg output:
> > > rock: directory entry would overflow storage
> > > rock: sig=0x4543, size=28, remaining=0
> > > rock: directory entry would overflow storage
> >
> > Seems that I am unable to read. It's the new rock-ridge bounds
> > checking.
> >
> > It worked for me. Is someone able to get an image of a failing
> > filesystem into my hands?
>
> I can reproduce it with the following:
>
> mkdir temp
> touch temp/file1 temp/file2 temp/file3
> mkisofs -R -l temp > test.iso
> mount -o loop /mnt/loop
Of course that should be: mount -o loop test.iso /mnt/loop :)
\__ Jason Munro
\__ [email protected]
\__ http://hastymail.sourceforge.net/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
