From: "Björn JACKE" <bj@sernet.de>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
LKML <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, Steve French <sfrench@samba.org>,
linux-fsdevel@vger.kernel.org,
Unix Support <unix-support@ucs.cam.ac.uk>
Subject: Re: CIFS: Rename bug on servers not supporting inode numbers
Date: Fri, 4 Nov 2011 12:16:36 +0100 [thread overview]
Message-ID: <E1RMHlS-00HYp9-Hk@intern.SerNet.DE> (raw)
In-Reply-To: <9A609E6D-DF91-4AF9-855A-6D28E9B95D15@cam.ac.uk>
On 2011-11-03 at 15:20 +0000 Anton Altaparmakov sent off:
> Hi,
>
> Our CIFS server problems seem to have no end… The Novell CIFS server does not support server inode numbers (when I try the mount option I get the message it is being turned off as server does not support it) and thus each inode gets a different number each time it is accessed and it gets a different number again for each readdir call.
>
> The fun happens with rename() when the rename source and target only differ in case, e.g.
>
> touch foo
> mv foo Foo
somehow related seems https://bugzilla.kernel.org/show_bug.cgi?id=39512
(as long as kernel bugzilla is dead, see
http://www.linux.sgi.com/archives/xfs-masters/2011-07/msg00022.html )
Case insensitive filesystems seem to be a problem in general on Linux. Not sure
how far kernel and/or glibc are involved in the problem. As a workaround for
the mess you need to do a temporary rename to a different name (not just a case
equivalent name).
Björn
--
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
parent reply other threads:[~2011-11-04 11:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9A609E6D-DF91-4AF9-855A-6D28E9B95D15@cam.ac.uk>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1RMHlS-00HYp9-Hk@intern.SerNet.DE \
--to=bj@sernet.de \
--cc=aia21@cam.ac.uk \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=unix-support@ucs.cam.ac.uk \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox