[lkml]   [2002]   [Sep]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.18: Re-read table failed with error 16: Device or resource busy - error
> What I did was to add a partition on a disk that has other mounted (e.g. root) 
> partitions on it. I did not change the numbering or positions of any of the
> partitions in use.The new partition was simply added after all existing
> partitions.
> So the question is why does the kernel deny to reread the partiton table and
> force me to reboot instaed of simply doing the reread? Are there any good
> reasons for this "bad" behaviour?

You credit the partition code with a little more intelligence than it
actually has. The problem is also a little harder than it seems when you
add partitions that might change the order of stuff.

The LVM layer supports dynamically resizing volumes, adding new volumes
and the like. Thats probably the right way to go for such things

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:53    [W:0.031 / U:0.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site