Messages in this thread | | | Date | Mon, 20 Oct 2003 13:26:26 -0400 (EDT) | From | "Calin A. Culianu" <> | Subject | Re: Rereading the Partition Table (ioctl BLKRRPART) |
| |
On Mon, 20 Oct 2003, Andreas Dilger wrote:
> On Oct 20, 2003 11:38 -0400, Calin A. Culianu wrote: > > Anyhow, in my quest to keep my uptime as high as possible, I was wondering > > how feasible it would be to make the BLKRRPART ioctl a little more > > flexible, so that in some cases a reboot wouldn't be required. > > > > Well, what do you guys think? I am tempted to just hack the sources now > > to get this working for myself, but before I start I am afraid maybe the > > situation isn't quite so simple... or there might be something I am > > overlooking. Can someone with more experience in the kernel share their > > thoughts on this? > > It already exists, and newer partition editors already support this. I > think parted and partx will use the new partition ioctls to change the > kernel's partition table without a reboot. Sadly, no documentation on > how to use partx.
Really? Coolness.. so the onus is on the userspace process to specify which partitions are suspected of having changed? Is that the reason for a new ioctl?
Just out of curiousity: What was the motivation for adding a new ioctl? What would have been wrong with also hacking BLKRRPART to behave this way, as in, have it figure out if a re-read is possible based on the heuristics I already suggested...
-Calin
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |