2.4.18: Re-read table failed with error 16: Device or resource busy - error

From: Rainer Krienke (krienke@uni-koblenz.de)
Date: Wed Sep 18 2002 - 01:51:10 EST

Hash: SHA1


I am Ruinning a (SuSE patched) 2.4.18 kernel and encountered the fdisk
repartition problem mentioned above. I know that I could solve the problem by
rebooting but I am interested if this is really needed since in my case a
data recovery job was finally killed after 12 hours because there was not
enough RAM or SWAP. I saw already very early that there could be a problem
with swap and there was enough unpartitioned disk space to add swap, but the
kernel would not let me.

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
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?

- --
- ---------------------------------------------------------------------------
Rainer Krienke, Universitaet Koblenz, Rechenzentrum
Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312
Mail: krienke@uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke
Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html
- ---------------------------------------------------------------------------
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org


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/

This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:22 EST