[SLE] Partioning the file system.
I recently acquired a second hard disk, and am in the process of adding it to my system. I am the only user of the system, and will probably add any new software into /usr/local. My original SuSE system is all mounted under /, in /dev/sda4. I decided that I would like to mount /usr on the new disk, under /dev/sdb4. I successfully partitioned and formatted the disk, and mounted a directory /temp on /dev/sdb4. Following the tip in the tips howto, I succeeded in copying the file system from /usr to /temp. My strategy was to be as follows: Updated the inittab to runlevel 2 - I did not want any problems with X, and I see that it is under /usr. Updated the fstab to mount /usr on /dev/sdb4 renamed /usr to /oldusr (I planed to delete /oldusr after everything checked out). shutdown -r now. On the shutdown, I get a few errors. I would expect this, as /usr has vanished from the face of the earth. On restart, I find that the mount for /usr fails, and I am left with a sick system. I checked the fstab, and it looks o.k. I renamed /oldusr to /usr to recover the system, and restarted. This time, I find that the mount of /usr to /dev/sdb4 is successful, and the system starts with /usr on the new disk. I've tried this a few times now, and the situation is consistent. If I rename /usr, I cannot mount a new usr. If I do not rename /usr, I can mount the new usr, but I cannot access the old /usr to reclaim the space. In both scenarios the space used on my old disk remains at 69%. I've checked the man pages, and the sdb, and the howtos, and cannot see anything obvious that I am doing wrong. I'm sure that I've seen some similar things in this mailing list previously, but I could not seem to find a searchable archive on the SuSE site. If anybody has had this situation or something similar before, I would appreciate to hear how they overcome this, and if not, has anyone any ideas of the approach I should take to try and nail this down?? Best regards. . . Fred -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
hi all
My strategy was to be as follows: Updated the inittab to runlevel 2 - I did not want any problems with X, and I see that it is under /usr. Updated the fstab to mount /usr on /dev/sdb4 renamed /usr to /oldusr (I planed to delete /oldusr after everything
your approach is fine, but by renaming /usr /oldusr you made the mount point for dev/sdb4 unaccessible. (since /usr is not there anymore.) i think you should rename usr to oldusr and create a new (empty) directory with the name of /usr.
checked out). shutdown -r now.
On the shutdown, I get a few errors. I would expect this, as /usr has vanished from the face of the earth. On restart, I find that the mount for /usr fails, and I am left with a sick system. I checked the fstab, and it looks o.k.
I renamed /oldusr to /usr to recover the system, and restarted. This time, I find that the mount of /usr to /dev/sdb4 is successful, and the system starts with /usr on the new disk.
I've tried this a few times now, and the situation is consistent. If I rename /usr, I cannot mount a new usr. If I do not rename /usr, I can mount the new usr, but I cannot access the old /usr to reclaim the space. In both scenarios the space used on my old disk remains at 69%.
I've checked the man pages, and the sdb, and the howtos, and cannot see anything obvious that I am doing wrong. I'm sure that I've seen some similar things in this mailing list previously, but I could not seem to find a searchable archive on the SuSE site.
If anybody has had this situation or something similar before, I would appreciate to hear how they overcome this, and if not, has anyone any ideas of the approach I should take to try and nail this down??
Best regards. . . Fred
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Thanks Robert, sometimes it's not easy to see the obvious. Of course everything worked fine after createing an empty /usr. Sorry about the waste of bandwidth. Best regards. . . Fred Robert Alexander Stragies wrote:
your approach is fine, but by renaming /usr /oldusr you made the mount point for dev/sdb4 unaccessible. (since /usr is not there anymore.) i think you should rename usr to oldusr and create a new (empty) directory with the name of /usr.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (2)
-
fredm@mail.telepac.pt
-
rost0005@stud.uni-sb.de