"WARNING: Re-reading the partition table failed with error 22: Invalid argument."
 

[root@herculetest ~]#
[root@herculetest ~]# fdisk /dev/vg0/space29
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.


The number of cylinders for this disk is set to 1032.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n
Command action
e extended
p primary partition (1-4)
e
Partition number (1-4): 1
First cylinder (1-1032, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1032, default 1032):
Using default value 1032

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.
[root@herculetest ~]#



WARNING: Re-reading the partition table failed with error 22: Invalid argument.


Is there a problem ? Or should it be fine only with a reboot ? If it's a problem, how do I fix it and what did I do wrong ?

I see on the internet that this error appears to alot of people.

Hi,

You should perform work on a valid device. What does your output for dmesg show for your storage that you wish too partition? Your not going to perform a partitioning on a filesystem but on a device so you can create a filesystem. :)

You know what I think ? I think there's nothing wrong with that, it's just a warning that the kernel started to use the new table, which I can tell by the time that the partition already changed to Linux LVM (8E).

Are you really sure it's a problem ?

I have 800GB HD and I created physical volume in which I have created logical volumes of eight gigs which are for informix, those lv are pointed to raw devices (character devices) in which informix is working in them. Informix was stopped at the time I was trying to do fdisk /dev/vg0/space1 in which vg0 is my physical volume group and the space is the lv.

This usually happens if the device does not contain a dos partition. You can use the 'o' switch in 'fdisk' to create an empty dos partition table and then use fdisk again to create the new partition.

after creating the partitons, use 'partprobe' to make the kernel use the new partition table.

This one's old. I have different problems now. But, anyway, that wasn't really a problem, as the "error" says, the new table will be used after reboot, that's why the linux dosen't read the partition immediately after I created it. I didn't want any "extension" if you may, on the partition, I mean like dos, ext2, fat32 etc. I just needed to create logical volumes in character mode for an informix server, which I successfully did.

Thread closed. But, thankx anyway.





WARNING: Re-reading the partition table failed with error 22: Invalid argument.

Hi,

Then mark the Thread as [Solved] via the 'Thread Tools'.