Regards,
YB Tan Sri Dato' Sri Adli a.k.a Dell
my.linkedin.com/pub/yb-tan-sri-dato-sri-adli-a-k-a-dell/44/64b/464/
H/p number: (017) 362 3661
________________________________
From: Mike Burger <mburger@xxxxxxxxxxxxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Sent: Wednesday, April 17, 2013 8:47 PM
Subject: Re: partprobe command showing error
Not on the boot disk.
--
Mike Burger
http://www.bubbanfriends.org
"It's always suicide-mission this, save-the-planet that. No one ever just
stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
> Thanks for the reply...
>
> But isn't it true that if I use partprobe command, I don't need to reboot
> my machine for kernel to read partition changes?
>
>
> On Wed, Apr 17, 2013 at 5:49 PM, Mike Burger
> <mburger@xxxxxxxxxxxxxxxxx>wrote:
>
>> > Hi,
>> >
>> > I've created a new partition on /dev/sda on my CentOS machine after
>> which
>> > fdisk -l gives output as:
>> > Device Boot Start End Blocks Id System
>> > /dev/sda1 * 1 13 104391 83 Linux
>> > /dev/sda2 14 3500 28009327+ 83 Linux
>> > /dev/sda3 3501 6527 24314377+ 83 Linux
>> >
>> > Now, when I run partprobe I get the following error:
>> > Error: Error informing the kernel about modifications to partition
>> > /dev/sda3 -- Device or resource busy. This means Linux won't know
>> about
>> > any changes you made to /dev/sda3 until you reboot -- so you shouldn't
>> > mount it or use it in any way before rebooting.
>> > Warning: The kernel was unable to re-read the partition table on
>> /dev/sda
>> > (Device or resource busy). This means Linux won't know anything about
>> the
>> > modifications you made until you reboot. You should reboot your
>> computer
>> > before doing anything with /dev/sda.
>> >
>> > I'm using parted rpm version "parted-1.8.1-29.el5". Is it some issue
>> with
>> > this version or with the way I'm using this command?
>>
>> In my experience, this is normal behavior...it's not any different than
>> if
>> you used fdisk, instead.
>>
>> You're modifying the partition table on the boot drive, and, if I recall
>> correctly, there isn't a mechanism for the kernel to reread the
>> partition
>> table of the boot drive.
>>
>> Long story short, you'll need to reboot.
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> http://lists.centos.org/mailman/listinfo/centos
>>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
