| To: | mark <mark.newman2@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: probs with cp -p |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Wed, 5 Jun 2002 11:34:50 +1000 |
| Cc: | "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <20020604132759.L13201@plato.local.lan>; from erbenson@alaska.net on Tue, Jun 04, 2002 at 01:27:59PM -0800 |
| References: | <200206032201.36167.mark.newman2@ntlworld.com> <20020604115218.D232510@wobbly.melbourne.sgi.com> <200206041056.45746.mark.newman2@ntlworld.com> <20020604132759.L13201@plato.local.lan> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Tue, Jun 04, 2002 at 01:27:59PM -0800, Ethan Benson wrote: > On Tue, Jun 04, 2002 at 10:56:45AM +0000, mark wrote: > > > > Okay I have now tried a vanilla 2.4.18 with XFS 1.1 kernel (just to ensure > > it > > wasnt a problem with my patched 2.4.19) with similar results. 'Argument > > too > > long' dissapeared but I still get the 'invalid argument' message. Could > > there be some kind of problem with my filesystem. I doubt it, this error is more likely a coding issue in the kernel, rather than an on-disk problem. > > Is there more info I could provide? > > i think he meant try current cvs as of yesterday, it looks There have been several related fixes, incl. yesterdays fix - please try a current CVS kernel, Mark & let me know if it still fails. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE - xfsprogs, Nathan Scott |
|---|---|
| Next by Date: | Re: [2.5.20-dj1]ld: cannot open xfs_dmapi/built-in.o: No such file or directory, Fabrice Ferrero |
| Previous by Thread: | Re: probs with cp -p, Ethan Benson |
| Next by Thread: | Re: probs with cp -p, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |