| To: | "Zhifeng F. Chen" <zffchen@xxxxxxxxx> |
|---|---|
| Subject: | Re: NFS and XFS again. |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | 30 Jan 2002 16:14:23 -0600 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <011101c1a9cc$53acf170$906a7080@divine> |
| References: | <011101c1a9cc$53acf170$906a7080@divine> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
What exactly are you doing? (linking what to what?) ENAMETOOLONG can arise when namelen >= MAXNAMELEN, which is #defined as 256... Can you show me the steps to duplicate the problem here? -Eric On Wed, 2002-01-30 at 14:25, Zhifeng F. Chen wrote: > Hi, > > I've met a problem with NFS and XFS combo. When I make a symbolic link on > /home/user/.../..., sometimes I met "File name too long" error. What's wrong > with it? -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Oops in bdflush with 2.4.1[4|7]-xfs, Eric Sandeen |
|---|---|
| Next by Date: | Re: Oops in bdflush with 2.4.1[4|7]-xfs, Nathan Poznick |
| Previous by Thread: | NFS and XFS again., Zhifeng F. Chen |
| Next by Thread: | Oops in bdflush with 2.4.1[4|7]-xfs, Nathan Poznick |
| Indexes: | [Date] [Thread] [Top] [All Lists] |