mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tobias Mantel <mantel@imago.de>
To: linux-kernel@vger.kernel.org
Cc: mantel@imago.de
Subject: Problem with stat and nfsmounts using kernel 2.6.21+
Date: Tue, 10 Jul 2007 13:02:39 +0200	[thread overview]
Message-ID: <4502119.20070710130239@x-organizer.de> (raw)

Hello,

I've got a problem with stat (/usr/bin/stat) after updating my linux kernel from 2.6.18 to 2.6.21.3
The problem appeared while using find with the -mount option to exclude files which are not at the local drive.

With kernel 2.6.18 the command "find / -mount" stayed at local disc and didn't go down in paths mounted via nfs to my local filesystem.
After updating to kernel version 2.6.21.3 find no longer stays at local drive and goes down in all paths mounted via nfs.
I recognized that stat now no longer handles filesystems mounted via nfs to / with a different device id. The device id is the same as for /

Example:

Linux 2.6.18 (ok)
------------------------
stat / | grep Device
Device: ch/12d  Inode: 552417276   Links: 26

/usr/www/tmp is mounted using nfs
stat /usr/www/tmp/ --filesystem | grep Type
ID: 0        Namelen: 255     Type: nfs
stat /usr/www/tmp/ | grep Device
Device: 17h/23d Inode: 671557496   Links: 2

/tmp/ is another partition at local disc mounted to /
stat /tmp/ --filesystem | grep Type
ID: 305      Namelen: 255     Type: xfs
stat /tmp/ | grep Device
Device: 305h/773d       Inode: 128         Links: 6

other linux box

Linux 2.6.21.3 (not ok)
---------------------------------
stat / | grep Device
Device: eh/14d  Inode: 1208534959  Links: 26

/usr/www/tmp is mounted using nfs
stat /usr/www/tmp/ --filesystem | grep Type
ID: 0        Namelen: 255     Type: nfs
stat /usr/www/tmp/ | grep Device
Device: eh/14d  Inode: 671557496   Links: 2

/tmp/ is another partition at local disc mounted to /
stat /tmp/ --filesystem | grep Type
ID: 805      Namelen: 255     Type: xfs
stat /tmp/ | grep Device
Device: 805h/2053d      Inode: 128         Links: 5

I have another box running with 2.6.20 and it behaves like the box running 2.6.18, everthing works fine.

Since no other changes than the kernel update was performed at the server, I think maybe sothing changed between 2.6.20 and 2.6.21 which leeds stat zu no longer mountet nfs shares with other device ids than the root device id.

I'm using SUSE LINUX 10.1 with a custom kernel form kernel.org.
Hopefully someone can give me a hint or can confirm my notice.

Because I have not subscribed the linux kernel mailing list, please send answers in CC to: mantel@imago.de
If somebody needs futher information or tests, please let me know.

Thank you so far and may linux/opensource live forever.

Kind regards,

 Tobias Mantel
Systemadministration/Netzwerk
Junior Level Linux Professional (LPIC-1)

------------------------------------------------------------------
Imago Informationstechnologie GmbH
Sauerwiesen 6
67661 Kaiserslautern
tel. 06301-708-139
fax. 06301-708-222
mailto:mantel@imago.de
http://www.imago.de
HRB 3008 Amtsgericht Kaiserslautern
USt-IdNr.: DE 174941022
Geschäftsführer: Herr Dipl.-Ing. Christian Keller 

                 reply	other threads:[~2007-07-10 11:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4502119.20070710130239@x-organizer.de \
    --to=mantel@imago.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®