Re: partman problems (sparc and elsewhere)
On Wed, Dec 01, 2004 at 03:07:54PM +0100, Sven Luther wrote:
> > 1. Partman may not write all partition tables - some of them may be for
> > example USB disk we are installing from
>
> So what ?
The following is a quote from
http://lists.debian.org/debian-boot/2004/debian-boot-200402/msg01788.html
* When it writes the partition data, I always get this error from
partman:
The kernel was unable to re-read the partition table on
/dev/scsi/host1/bus0/target0/lun0/disk (Device or resource busy).
That is the usb device I booted the installer from, and I did not tell
partman to do anything with it (nor does it), so I do not know why it
displays this message.
> > 2. Consequently partman may try to write only the partition tables that
> > contain partitions that will be used somehow by the new Debian
> > (partitions with some file system, with swap or booting partition)
>
> Well, the idea is to write the system type only for the partition we are
> formating, not ?
Or partition we are mounting without formating if its type doesn't
correspond to the file system it contains.
> > 3. But if the user uses LVM or RAID partman has to write the partition
> > tables before it knows which of them will be used. Latter they are
> > already in use and the kernel complains about changes in them
>
> And ? You simply do the system flag writing at the same time you format the
> partitions, provided they are not on a LVM or RAID device ?
At the time when some partition is being formatted (or simply sceduled
for mounting) the partition table may already contain physical volumes
of activated volume groups.
Anton Zinoviev
Reply to: