| To: | "Seth Mos" <knuffie@xxxxxxxxx> |
|---|---|
| Subject: | Re: UPDATE: VERY URGENT: "cp -a" creates mysteriously "hidden" files?! |
| From: | "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx> |
| Date: | Sat, 29 Dec 2001 21:55:11 +0100 |
| Cc: | "Linux XFS Mailing List" <linux-xfs@xxxxxxxxxxx>, "Eric Sandeen" <sandeen@xxxxxxx> |
| In-reply-to: | <Pine.BSI.4.10.10112291552030.28220-100000@xs4.xs4all.nl> |
| Reply-to: | "Ralf G. R. Bergs" <rabe@xxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Sat, 29 Dec 2001 16:08:24 +0100 (CET), Seth Mos wrote:
>It's possible you might had checked out a CVS tree just in between two
>fixes where it was broken.
Ok, I've now built a new kernel based upon today's CVS source.
Guess what? The problem's still there, but it seems that things have become
somewhat better. I only received THREE error messages like the following:
ls: ./path/to/some/file: No such file or directory
when invoking "ls -laRh" in the directory where the RAID is mounted. With
previous kernels I would typically receive dozens of errors (there are some
543,000 files on the respective filesystem.)
Based upon this findings I think we can for sure rule out a broken kernel
release. It must be a systematic bug in the XFS(?) code that hasn't been fixed
so far. But how can we find the location?!
Thanks,
Ralf
--
Verkaufe Original-BMW-Raeder: L I N U X .~.
http://adsl-bergs.rz.rwth-aachen.de/~rabe The Choice /V\
of a GNU /( )\
Generation ^^-^^
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: UPDATE: VERY URGENT: "cp -a" creates mysteriously "hidden" files?!, Ralf G. R. Bergs |
|---|---|
| Next by Date: | Re: UPDATE: VERY URGENT: "cp -a" creates mysteriously "hidden" files?!, Seth Mos |
| Previous by Thread: | Re: UPDATE: VERY URGENT: "cp -a" creates mysteriously "hidden" files?!, Ralf G. R. Bergs |
| Next by Thread: | Re: UPDATE: VERY URGENT: "cp -a" creates mysteriously "hidden" files?!, Seth Mos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |