On 2/27/07, dan1 <address@hidden> wrote:
hello.
I have just seen a strange behaviour with chroot on a system using CentOS
4.4, with root being /dev/md2, and trying to chroot to another drive
array which is /dev/md22.
When doing this with the following command:
chroot /my_folder_with_md22
What was the content of /my_folder_with_md22/etc/mtab before you
entered the chroot command? What device numbers and inodes do you
get if you stat the various directories?
then, the chroot indicates that the mounted device is not md22 but md12:
# mount
/dev/md12 on / type ext3 (rw)
I also have a md12 array on this system.
It seems that chroot is mixing things up. However, if I place a file on
the /dev/md22 array, and then chroot to it, the file is really present
there, but the mount command still reports to be using the /dev/md12
array.
It's the first time I use this command, so I might also do something
wrong, but it doesn't seem so.
Thanks in advance for any bug confirmation.