Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Feb 1995 13:53:28 -0800 (PST)
From:      "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
To:        jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi)
Cc:        freebsd-bugs@freefall.cdrom.com
Subject:   Re: ls -R does not recurse (on cdrom)
Message-ID:  <199502212153.NAA22649@gndrsh.aac.dev.com>
In-Reply-To: <9502212136.AA12486@cabri.obs-besancon.fr> from "Jean-Marc Zucconi" at Feb 21, 95 10:36:14 pm

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> >>>>> "Rodney" == Rodney W Grimes <rgrimes@gndrsh.aac.dev.com> writes:
> 
>  >> 
>  >> 'ls -R /cdrom' sometimes lists only the /cdrom directory and does not
>  >> recurse, but 'ls -lR /cdrom' works. This nevers happens after a
>  >> reboot, but only  after a number of file access on the cdrom. One
>  >> can trigger the bug with eg. 'find /cdrom -type f -exec file {} \;' 
> 
>  > For the find problem we need to pull over some patches made to 1.X find,
>  > try this and let me know if it works for you (I don't have a cdrom
>  > on a 2.x system here :-().
> 
> The find command works, it is just used to access files so that 'ls'
> fails. You can try on freefall, this happens here too:
> Script started on Tue Feb 21 13:32:40 1995
> bash$ ls -R /cdrom |wc
>       11      11      90
> bash$ ls -R /cdrom |wc
>      297     285    2960
> bash$ ls -R /cdrom |wc
>       74      69     750
> bash$ ls -R /cdrom |wc
>       11      11      90
> bash$ ls -R /cdrom |wc
>      268     258    2640
> bash$ ls -R /cdrom |wc
>       11      11      90
> bash$ ls -R /cdrom |wc
>      335     320    3413
> bash$ hostname
> freefall.cdrom.com
> bash$ exit
> 
> Script done on Tue Feb 21 13:33:26 1995

Find does not work correctly on freefall, some times it only gives
you the top level directory, some times it gives you 2 or 3 levels,
it is as sparodic as ls -R :-(.

Try these on freefall to see what I mean:
cd /cdrom
find .
find .
find .
find /cdrom
find /cdrom
find /cdrom

You'll notice different output depending on what it feels like doing
at that moment.  Some of this is very similiar to the problems we once
had in 1.X.

>  > Find /cdrom -fstype cd9660 -type f -exec file {} \;
> 
> cd9660 is an unsupported type! ("find: cd9660: unknown file type")

:-(, okay, I was the one who added the fstype isofs to 1.x find, probably
should pull those changes into the 2.x find.  Though this is probably not
the problem we are seeing, I suspect that cd9660 is as broken as ever :-(.

> 
>  > This may be the default file system type used by find not containing
>  > cd9660 (this was the problem in 1.x, only it was missing isofs).

Looks like it is time to move my cdrom drive from my old 1.x system over
to one of my 2.x test boxes.  I really don't have time to go after this
one, so if you want to track it down and squash it by all means go ahead.

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                   Custom computers for FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502212153.NAA22649>