GNU bug report logs - #35167
About chroot some question on centos6 kernel:

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35167 in the body.
You can then email your comments to 35167 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "往事随风" <gin9145yan <at> sina.com>
To: "bug-coreutils" <bug-coreutils <at> gnu.org>
Subject: About chroot some question on centos6 kernel:
Date: Sat, 06 Apr 2019 11:09:50 +0800

[Message part 1 (text/plain, inline)]

OS centos6.10
kernel vmlinuz-2.6.32-754.el6.x86_64
hello!
grub-install  in a new disk /mnt/boot;copy /bin/bash and *.so ; chroot /mnt/sysroot is ok!exit and ctrl+d
use the new disk startup,
"dracut warning can't mount root filesystemmount :/dev/sda3 already mounted or /sysroot busy
mount: according to mtab, /dev/sdb3 is already mounted on /mnt/sysroot"
don't chroot /mnt/sysroot 
startup ——success

why?!  I don't now! 

thank you

[Message part 2 (text/html, inline)]

Message #8 received at 35167 <at> debbugs.gnu.org (full text, mbox):

From: Bob Proulx <bob <at> proulx.com>
To: 往事随风 <gin9145yan <at> sina.com>
Cc: 35167 <at> debbugs.gnu.org
Subject: Re: bug#35167: About chroot some question on centos6 kernel:
Date: Sun, 21 Apr 2019 22:56:52 -0600

close 35167
thanks

Hello 往事随风,

往事随风 wrote:
> OS centos6.10
> kernel vmlinuz-2.6.32-754.el6.x86_64
> hello!
> grub-install  in a new disk /mnt/boot;copy /bin/bash and *.so ; chroot /mnt/sysroot is ok!exit and ctrl+d

Sounds like 'chroot' worked correctly in the above sequence.

> use the new disk startup,
> "dracut warning can't mount root filesystemmount :/dev/sda3 already mounted or /sysroot busy
> mount: according to mtab, /dev/sdb3 is already mounted on /mnt/sysroot"
> don't chroot /mnt/sysroot 
> startup ——success
> 
> why?!  I don't now! 

I have no idea either.

This does not look like a bug report for the 'chroot' command from the
GNU Coreutils project however.  It looks like a bug report against
'dracut'.  As such there isn't anything that we can do about it here.
I think that is why no one else of the team responded.  It didn't seem
like anything that anyone here could do anything about.

Also the chroot command line utility is simply a thin wrapper around
the chroot(2) kernel system call.  It does whatever the kernel does.

Therefore I am going to close the bug in our ticket system.  However
please do respond and add any further discussion.  We will see it.  If
something looks like a bug the ticket will be re-opened.

Bob

Message #11 received at 35167-quiet <at> debbugs.gnu.org (full text, mbox):

From: "往事随风" <gin9145yan <at> sina.com>
To: "Bob Proulx" <bob <at> proulx.com>
Subject: 回复:Re: bug#35167: About chroot some question on centos6 kernel:
Date: Mon, 22 Apr 2019 13:18:57 +0800

[Message part 1 (text/plain, inline)]

Hello Bob Proulx
sorry!It's not a bug! use the command mount -n is ok!
Thank you very much and sorry for that!

----- 原始邮件 -----
发件人: Bob Proulx<bob <at> proulx.com>
收件人: 往事随风<gin9145yan <at> sina.com>
抄送人: 35167<35167 <at> debbugs.gnu.org>
主题: Re: bug#35167: About chroot some question on centos6 kernel:
日期: 2019-4-22 12:56

close 35167
thanks
Hello 往事随风,
往事随风 wrote:
> OS centos6.10
> kernel vmlinuz-2.6.32-754.el6.x86_64
> hello!
> grub-install in a new disk /mnt/boot;copy /bin/bash and *.so ; chroot /mnt/sysroot is ok!exit and ctrl+d
Sounds like &#39;chroot&#39; worked correctly in the above sequence.
> use the new disk startup,
> "dracut warning can&#39;t mount root filesystemmount :/dev/sda3 already mounted or /sysroot busy
> mount: according to mtab, /dev/sdb3 is already mounted on /mnt/sysroot"
> don&#39;t chroot /mnt/sysroot 
> startup ——success
> 
> why?! I don&#39;t now! 
I have no idea either.
This does not look like a bug report for the &#39;chroot&#39; command from the
GNU Coreutils project however. It looks like a bug report against
&#39;dracut&#39;. As such there isn&#39;t anything that we can do about it here.
I think that is why no one else of the team responded. It didn&#39;t seem
like anything that anyone here could do anything about.
Also the chroot command line utility is simply a thin wrapper around
the chroot(2) kernel system call. It does whatever the kernel does.
Therefore I am going to close the bug in our ticket system. However
please do respond and add any further discussion. We will see it. If
something looks like a bug the ticket will be re-opened.
Bob
来自新浪邮箱触屏版

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.