linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars <sunberg@gmail.com>
To: linux-admin@vger.kernel.org, focus-linux@securityfocus.com
Subject: Question about inodes
Date: Mon, 28 Jul 2008 09:17:30 +0200	[thread overview]
Message-ID: <8f2fc6f50807280017y3e8d5625u1ab07c116133c20e@mail.gmail.com> (raw)

Hello!

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

[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

[root@test ~]# ls /sys/
	block  bus  class  devices  firmware  fs  kernel  module  power

[root@test ~]# ls /dev/pts/
	0

[root@test ~]# stat /sys/ ; stat /dev/pts
	  File: `/sys/'
	  Size: 0               Blocks: 0          IO Block: 4096   directory
	Device: 0h/0d   Inode: 1           Links: 11
	Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
	Access: 2008-07-28 07:51:41.543581362 -0100
	Modify: 2008-07-25 13:06:46.705937679 -0100
	Change: 2008-07-25 13:06:46.705937679 -0100
	  File: `/dev/pts'
	  Size: 0               Blocks: 0          IO Block: 4096   directory
	Device: bh/11d  Inode: 1           Links: 2
	Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
	Access: 2008-07-28 07:51:53.067829410 -0100
	Modify: 2008-07-25 13:06:46.707937375 -0100
	Change: 2008-07-25 13:06:46.707937375 -0100

[root@larscen ~]# fdisk -l
	Disk /dev/hda: 40.0 GB, 40020664320 bytes
	255 heads, 63 sectors/track, 4865 cylinders
	Units = cylinders of 16065 * 512 = 8225280 bytes

	   Device Boot      Start         End      Blocks   Id  System
	/dev/hda1   *           1          13      104391   83  Linux
	/dev/hda2              14        4865    38973690   8e  Linux LVM

[root@test ~]# uname -a
Linux test 2.6.18-92.el5 #1 SMP Tue Jun 10 18:49:47 EDT 2008 i686 i686
i386 GNU/Linux


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..

I searched for a couple of more inodes (find / -inum NUMBER) to find
out that this is very common..

The OS is centos5, but the same seems to be the case on debian.


Side question: How many % used inodes critical to much? I have a
server that have around 66% used inodes,
and wonder if I should do something or if I should let the problem fix itself.

Thanks
  Lars

             reply	other threads:[~2008-07-28  7:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28  7:17 Lars [this message]
2008-07-28 10:15 ` Question about inodes Adam T. Bowen
2008-07-28 11:59 ` Glynn Clements

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=8f2fc6f50807280017y3e8d5625u1ab07c116133c20e@mail.gmail.com \
    --to=sunberg@gmail.com \
    --cc=focus-linux@securityfocus.com \
    --cc=linux-admin@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).