From: "Paul Rolland" <rol@as2917.net>
To: "'LKML'" <linux-kernel@vger.kernel.org>
Subject: Why is /dev on a different filesystem ? [Kernel 2.6.20.3]
Date: Wed, 21 Mar 2007 20:13:50 +0100 [thread overview]
Message-ID: <04ea01c76bed$11b0d050$4b00a8c0@donald> (raw)
Hello,
I was trying to backup a machine using tar and the --one-file-system option
and I was getting an archive without /dev, but tar was spitting :
/dev: file is on a different filesystem; not dumped
So, I had a look at the code in tar, and the comparison is done on the
stat.st_dev field...
I then wrote a simple program to stat("/", ...) and stat("/dev", ...),
and got :
For / :
st_dev : 769
st_ino : 2
st_mode : 16877
st_nlink : 23
st_uid : 0
st_gid : 0
st_rdev : 0
st_size : 4096
For /dev :
st_dev : 15
st_ino : 1117
st_mode : 16877
st_nlink : 23
st_uid : 0
st_gid : 0
st_rdev : 0
st_size : 165580
So, obviously, tar is right...
man 2 stat says :
The st_dev field describes the device on which this file resides.
and df -a reports :
[root@host-181 src]# df -a
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 7936256 3105556 4421048 42% /
proc 0 0 0 - /proc
sysfs 0 0 0 - /sys
devpts 0 0 0 - /dev/pts
tmpfs 517632 0 517632 0% /dev/shm
/dev/hda5 61787140 237360 58360480 1% /usr/local/witbe
/dev/hda2 4956316 142292 4558192 4% /var/log
none 0 0 0 -
/proc/sys/fs/binfmt_misc
So, obviously, /dev is on /, but the stat(2) says no.
Who is right, and where is the bug ?
Kernel 2.4 had it right : /dev was on /, no doubt.
Regards,
Paul
next reply other threads:[~2007-03-21 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 19:13 Paul Rolland [this message]
2007-03-21 19:20 ` Why is /dev on a different filesystem ? [Kernel 2.6.20.3] Valdis.Kletnieks
2007-03-21 19:30 ` Paul Rolland
2007-03-21 19:37 ` Greg KH
2007-03-21 19:59 ` David Schwartz
2007-03-21 20:58 ` Alistair John Strachan
2007-03-21 21:32 ` Andreas Schwab
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='04ea01c76bed$11b0d050$4b00a8c0@donald' \
--to=rol@as2917.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.