Skip to contentSkip to conversation

Why is /dev on a different filesystem ? [Kernel 2.6.20.3]

DISCUSSION Paul Rolland 6 participants 7 messages Mar 21, 2007

lore
Share & tools
lore
#0 lore 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

#1 lore raw
Quoted 5 lines · Paul Rolland

So, obviously, tar is right...
man 2 stat says :
The st_dev field describes the device on which this file resides.

Quoted 7 lines

and df -a reports :
[root@host-181 src]# df -a
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 7936256 3105556 4421048 42% /

So, obviously, /dev is on /, but the stat(2) says no. Who is right, and where is the bug ?

Might want to 'cat /proc/mounts', and ponder the fact that a filesystem can be mounted and not listed in /etc/mtab, and then see if your system has 'udev' installed and enabled.

#2 lore raw
Quoted 5 lines

Might want to 'cat /proc/mounts', and ponder the fact that a filesystem
can be mounted and not listed in /etc/mtab, and then see if your system
has 'udev' installed and enabled.

Damn ! You're right :
cat /proc/mounts | grep dev
none /dev tmpfs rw 0 0

and no, I don't have any udev running, still can't stand it ;)

Thx for the pointer, I was too much trusting df :(

Regards,
Paul

#3 lore raw
In reply to Paul Rolland
Quoted 5 lines · Paul Rolland

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

That is probably because your distro is using udev which usually means tmpfs is mounted at /dev/

Quoted 4 lines

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 :

What does /proc/mounts show?

thanks,

greg k-h

#4 lore raw
In reply to Paul Rolland
Quoted 5 lines

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.

Have a look at the contents of /proc/mounts and all will be clear.

DS

#5 lore raw
In reply to Paul Rolland
Quoted 4 lines · Paul Rolland

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.

Some distros will mount tmpfs over /dev so that a minimal "real dev" can be provided as a fallback, but udev can add and remove nodes from /dev ad hoc during regular runtime. So I don't think there's a bug and I don't think anything is lying.

If you want the dev your distro gave you, just mount your rootfs on another mount point in read-only and run tar over that instead.

Signature · 5 lines
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
#6 lore raw
In reply to Paul Rolland
Quoted 11 lines · Paul Rolland

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   -
Quoted 4 lines

/proc/sys/fs/binfmt_misc

So, obviously, /dev is on /, but the stat(2) says no. Who is right, and where is the bug ?

Try cat /proc/mounts, apparently when /dev was mounted /etc/mtab wasn't updated appropriately.

Andreas.

Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."