Re: [opensuse] Update problem
El 19/05/14 16:50, A. den Oudsten escribió:
op 19-05-14 22:40, Cristian Rodríguez schreef:
El 19/05/14 16:34, A. den Oudsten escribió:
I was not quite clear. In Yast KInfocenter I found the physical free memory is 507.92 MiB That does not usually matter much..if there is 500Mib free the system will work just fine.
and indeed the / filesystem is 13.87 GiB
Is 13.87GiB or has that amount of free space ? The update fails because there is not enough disk space to install an RPM..
/ filesystem has 12.78 GB in use; so it should be sufficient
Hrmmm.. that can't be .. UNLESS.. are you using BTRFS in combination with snapper ? -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/19/2014 06:12 PM, Cristian Rodríguez wrote:
El 19/05/14 16:50, A. den Oudsten escribió:
op 19-05-14 22:40, Cristian Rodríguez schreef:
El 19/05/14 16:34, A. den Oudsten escribió:
I was not quite clear. In Yast KInfocenter I found the physical free memory is 507.92 MiB That does not usually matter much..if there is 500Mib free the system will work just fine.
and indeed the / filesystem is 13.87 GiB
Is 13.87GiB or has that amount of free space ? The update fails because there is not enough disk space to install an RPM..
/ filesystem has 12.78 GB in use; so it should be sufficient
Hrmmm.. that can't be .. UNLESS.. are you using BTRFS in combination with snapper ?
Maybe. Maybe not. Modern systems require /usr to be mounted at boot and many systems configure that to be part of the root file system. There is a lot under /usr that really should not be on /, that can be part of a mounted file system. There are quite a number of databases that like there, ldap, dns, mysql. There is also all the things that live under /usr/share which aren't needed at boot time, which can be put on a mounted file system. Sadly, on a 'live' system that is being updated, you can't make things like /usr/share/doc read-only. One of the advantages of using LVM is that I can create a new logical volume to use as a partition, create a file system on it, migrate things like /usr/share onto it .... Admitted this can't be done indefinitely. But there is a lot that CAN be done to offload from / Just to check: Do you have these as separate file systems? /tmp /home /srv /boot /opt You can also have /usr as a separate file system if your initrd takes care of mounting it at boo. Perhaps someone can explain how to do that. -- Information is the currency of democracy. --Thomas Jefferson -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-05-20 03:14, Anton Aylward wrote:
You can also have /usr as a separate file system if your initrd takes care of mounting it at boo. Perhaps someone can explain how to do that.
It's automatic. I have it like that. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlN7IGQACgkQja8UbcUWM1xkgQD+J2yuY/qoBjMQVcaEw950LPlq mIPV++YRoPHvjvWQrgUA/AhTmqKo5p5dsS1H+SORNHNinyjal+GhP3HLrJtr7zWK =iD4r -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/20/2014 05:29 AM, Carlos E. R. wrote:
On 2014-05-20 03:14, Anton Aylward wrote:
You can also have /usr as a separate file system if your initrd takes care of mounting it at boo. Perhaps someone can explain how to do that.
It's automatic. I have it like that.
Ah, sorry, let me rephrase. If you install with a separate /usr its all taken care of automatically. However if you have /usr on the ROOTFS and want to create a new partition and migrate /usr to that then you'll need to create a new initrd that knows about this. Perhaps someone can explain how to do that. And possibly the best way to migrate /usr -- should one use 'cp', mv', 'cpio' or 'rsync' ? -- Growth for the sake of growth is the ideology of the cancer cell. -- Edward Abbey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-05-20 15:56, Anton Aylward wrote:
On 05/20/2014 05:29 AM, Carlos E. R. wrote:
It's automatic. I have it like that.
Ah, sorry, let me rephrase.
If you install with a separate /usr its all taken care of automatically.
However if you have /usr on the ROOTFS and want to create a new partition and migrate /usr to that then you'll need to create a new initrd that knows about this.
If you run "mkinitrd" it should do it. However, you have to do it after migration and before booting.
And possibly the best way to migrate /usr -- should one use 'cp', mv', 'cpio' or 'rsync' ?
I use 'mc' or 'rsync', with some parameters that I don't remember by memory. Probably these: rsync --archive --acls --xattrs --hard-links --stats \ --human-readable ORIGEN/ DESTINO And it has to be done from a live. Basically, the procedure is: create new partition, mount it somewhere, copy usr there, rename old usr, edit fstab appropriately, run mkinitrd inside a chroot (with new usr mounted appropriately). Reboot. Once checked, delete old usr directory. AND, always keep a rescue USB stick available, in case there are problems booting, now or in the future: consider that in rescue mode, few applications and libraries will be available, fewer that some years ago. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlN7ZLsACgkQja8UbcUWM1yoMgD9GQGmzQvpv9UlgnBLu0Z6kf4C NeeFBQwftQhOREFD4SMA/2cmKNs6IFNdU9eoTfSSZxDIBYAVrfw5sCkI1P7RcqbX =wZQI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/20/2014 10:20 AM, Carlos E. R. wrote:
On 2014-05-20 15:56, Anton Aylward wrote:
On 05/20/2014 05:29 AM, Carlos E. R. wrote:
It's automatic. I have it like that.
Ah, sorry, let me rephrase.
If you install with a separate /usr its all taken care of automatically.
However if you have /usr on the ROOTFS and want to create a new partition and migrate /usr to that then you'll need to create a new initrd that knows about this.
If you run "mkinitrd" it should do it. However, you have to do it after migration and before booting.
I was hoping you'd talk about the config and parameters needed. *sigh* As I understand it, mkinitrd is on the way out in favour of some other, easier to configure and manage, tool.
And possibly the best way to migrate /usr -- should one use 'cp', mv', 'cpio' or 'rsync' ?
I use 'mc' or 'rsync', with some parameters that I don't remember by memory. Probably these:
rsync --archive --acls --xattrs --hard-links --stats \ --human-readable ORIGEN/ DESTINO
And it has to be done from a live. Basically, the procedure is:
create new partition, mount it somewhere, copy usr there, rename old usr, edit fstab appropriately, run mkinitrd inside a chroot (with new usr mounted appropriately).
"Chroot"? Chroot to where? You can't, in my experience, simply chroot to anywhere except / without having to make provision for /dev, /proc and /sys. At the very least initrd needs to know what modules to include and where to write to. If you've chroot'd this may be all upset unless you either make a few mounts and symlinks and supply an argument list. Now to be fail, I've booted form the rescue disk to do many operations and then mounted the hard drive I've been modifying/repairing on /mnt/disk and chroot'd there so that I'm running on the 'real' system and not the rescue disk. Perhaps that's what you were thinking of but didn't mention or perhaps edited out when revision. If, however, you are doing this change in single user mode without booting from the rescue disk, then the chroot isn't needed. As with so many things when working with Linux, "there's more than one way to do things". However .... Migrating /usr/share to its own partition frees up space on /usr and maybe on /, and you don't need to run mkinited :-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-05-20 16:47, Anton Aylward wrote:
On 05/20/2014 10:20 AM, Carlos E. R. wrote:
If you run "mkinitrd" it should do it. However, you have to do it after migration and before booting.
I was hoping you'd talk about the config and parameters needed. *sigh*
Well, you see, I make them on the go. I know the goal, the tools, and I look up the exact syntax in the man pages. I make mistakes, so I go back and correct them, on the go. I have done it several times, successfully, and helped others correct their problems. But I don't have a precise writeup with detailed instructions that ensure success.
As I understand it, mkinitrd is on the way out in favour of some other, easier to configure and manage, tool.
So I heard... I'll wait. You people try it, then you tell me. I'll listen and take notes. >:-))
"Chroot"? Chroot to where?
You can't, in my experience, simply chroot to anywhere except / without having to make provision for /dev, /proc and /sys.
Then, do :-) Those a are menial details to be filled up later :-) Yes, you have to mount the target root somewhere, and the new usr partition in the correct place under that somewhere. And the separate boot partition if it exists, and var if it is separate, etc. And yes, you need bind mount sys, proc, dev - but you find that out if you forget from the error messages you get.
At the very least initrd needs to know what modules to include and where to write to. If you've chroot'd this may be all upset unless you either make a few mounts and symlinks and supply an argument list.
Well, initrd should know already about the needed modules, the hardware has not changed, nor disk driver, and probably not the filesystems used.
Now to be fail, I've booted form the rescue disk to do many operations and then mounted the hard drive I've been modifying/repairing on /mnt/disk and chroot'd there so that I'm running on the 'real' system and not the rescue disk. Perhaps that's what you were thinking of but didn't mention or perhaps edited out when revision.
Yes, that's exactly what I meant.
If, however, you are doing this change in single user mode without booting from the rescue disk, then the chroot isn't needed.
Yes, but I'm not sure that you can rename usr and mount the new one in place in that mode, because it is in use...
However ....
Migrating /usr/share to its own partition frees up space on /usr and maybe on /, and you don't need to run mkinited :-)
True. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlN7blQACgkQja8UbcUWM1w88AD/ewyiv3acni3fvL7AwjDAkaz3 A128TVkkfx1M5NVBj9MA/RIMrVFAeuPuNd+rabIu64XiQnqlBo/PQjSrW5rAPd5P =L8GH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Anton Aylward -
Carlos E. R. -
Cristian Rodríguez