From: Glynn Clements <glynn@gclements.plus.com>
To: Lars <sunberg@gmail.com>
Cc: linux-admin@vger.kernel.org, focus-linux@securityfocus.com
Subject: Re: Question about inodes
Date: Mon, 28 Jul 2008 12:59:16 +0100 [thread overview]
Message-ID: <18573.46228.266760.713436@cerise.gclements.plus.com> (raw)
In-Reply-To: <8f2fc6f50807280017y3e8d5625u1ab07c116133c20e@mail.gmail.com>
Lars wrote:
> I've always thought at indes as something uniq on every file on the
> same file system. Today, I saw something weird that tickled my theory
> about this. I found two folders, on the same filesystem that had the
> same indoe. It is inode 1. Here is some info..
>
>
> [root@test ~]# ls -lid /sys
> 1 drwxr-xr-x 11 root root 0 Jul 25 13:06 /sys
>
> [root@test ~]# ls -lid /dev/pts
> 1 drwxr-xr-x 2 root root 0 Jul 25 13:06 /dev/pts
Inode numbers are only unique within a filesystem. /sys and /dev/pts
are separate filesystems.
> [root@test ~]# df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/mapper/VolGroup00-LogVol00
> 36756152 2138060 32720828 7% /
> /dev/hda1 101086 11818 84049 13% /boot
> tmpfs 253652 0 253652 0% /dev/shm
"df" only lists filesystems which correspond to block devices. Use
"mount" or "cat /proc/mounts" for a complete list.
> As you see, both /sys and /dev/pts have the same inode. This is not an
> issue, but a question.
> I can see that the device is not the same on these two files/folders,
> but they are on the same fs..
No they aren't.
/proc, /proc/bus/usb, /sys, /dev, /dev/pts, and /dev/shm are usually
separate filesystems (/dev might not be if you're using static device
files rather than devfs).
--
Glynn Clements <glynn@gclements.plus.com>
prev parent reply other threads:[~2008-07-28 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 7:17 Question about inodes Lars
2008-07-28 10:15 ` Adam T. Bowen
2008-07-28 11:59 ` Glynn Clements [this message]
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=18573.46228.266760.713436@cerise.gclements.plus.com \
--to=glynn@gclements.plus.com \
--cc=focus-linux@securityfocus.com \
--cc=linux-admin@vger.kernel.org \
--cc=sunberg@gmail.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;
as well as URLs for NNTP newsgroup(s).