FS#136 - possible filesystem creation bug on setup script

Attached to Project: Arch Linux
Opened by (almostlucky2) - Wednesday, 13 August 2003, 18:49 GMT
Last edited by Judd Vinet (judd) - Sunday, 14 September 2003, 18:58 GMT
Task Type Bug Report
Category Installation
Status Closed
Assigned To Judd Vinet (judd)
Architecture All
Severity Medium
Priority Normal
Reported Version 0.6 Widget
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

When installing over various partitions (/ /boot /usr /home /var and /tmp all seperate) i would get stuck in a loop, prompting me to abort the install. All but home filesystems were created by the installer (home was just mounted).

This did not occur when i used only /boot /root and swap.
This task depends upon

Closed by  Judd Vinet (judd)
Wednesday, 18 August 2004, 15:50 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Tuesday, 06 April 2004, 21:10 GMT
/tmp is your problem.
Whenever you create and mount a /tmp with the installer, the installer umounts /tmp, which is tmpfs. The result will be an empty /tmp directory on a read-only filesystem, causing setup not being able to write in /tmp. The result is a dialog asking to abort.
Comment by Matt Toso (Takaitra) - Saturday, 29 May 2004, 20:38 GMT
I had this same problem during my first AL install last week. It almost scared me away. I didn't know the problem was with creating a /tmp partition but if I had known AL uses tmpfs by default I wouldn't have bothered creating a /tmp partition.
Comment by Judd Vinet (judd) - Tuesday, 01 June 2004, 02:17 GMT
I've added a note to the installer, mentioning that we use tmpfs and that the user should not create a /tmp partition.
Comment by Matt Toso (Takaitra) - Tuesday, 01 June 2004, 03:04 GMT
Great, that will prevent new AL users who like to make multiple partitions from running into a mysterious abort loop like I did. Thanks.

Loading...