Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #195849 > unrolled thread
| Started by | Mark Copper <mcopper@straitcity.com> |
|---|---|
| First post | 2018-05-18 01:10 +0200 |
| Last post | 2018-05-25 23:20 +0200 |
| Articles | 20 on this page of 53 — 20 participants |
Back to article view | Back to linux.debian.user
making more room in root partition for distribution upgrade Mark Copper <mcopper@straitcity.com> - 2018-05-18 01:10 +0200
Re: making more room in root partition for distribution upgrade bw <bwtnguy@yahoo.com> - 2018-05-18 01:40 +0200
Re: making more room in root partition for distribution upgrade Mark Copper <mcopper@straitcity.com> - 2018-05-18 02:10 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-20 10:30 +0200
Re: making more room in root partition for distribution upgrade Mark Copper <mcopper@straitcity.com> - 2018-05-21 18:20 +0200
Re: making more room in root partition for distribution upgrade Curt <curty@free.fr> - 2018-05-21 18:50 +0200
Re: making more room in root partition for distribution upgrade Mark Copper <mcopper@straitcity.com> - 2018-05-21 19:00 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-21 19:30 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-21 19:30 +0200
Re: making more room in root partition for distribution upgrade Mark Copper <mcopper@straitcity.com> - 2018-05-25 02:30 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-25 20:30 +0200
Re: making more room in root partition for distribution upgrade Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-18 03:10 +0200
Re: making more room in root partition for distribution upgrade Andy Smith <andy@strugglers.net> - 2018-05-18 03:30 +0200
Re: making more room in root partition for distribution upgrade Rick Thomas <rbthomas@pobox.com> - 2018-05-18 13:10 +0200
Re: making more room in root partition for distribution upgrade Andy Smith <andy@strugglers.net> - 2018-05-18 14:10 +0200
Re: making more room in root partition for distribution upgrade Felix Miata <mrmazda@earthlink.net> - 2018-05-18 05:00 +0200
Re: making more room in root partition for distribution upgrade ntrfug <ntrfug@cox.net> - 2018-05-19 16:30 +0200
Re: making more room in root partition for distribution upgrade Charlie S <taoquester@gmail.com> - 2018-05-20 08:00 +0200
Re: making more room in root partition for distribution upgrade songbird <songbird@anthive.com> - 2018-05-20 14:40 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-20 15:10 +0200
Re: making more room in root partition for distribution upgrade Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-20 16:30 +0200
Re: making more room in root partition for distribution upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2018-05-20 16:40 +0200
Re: making more room in root partition for distribution upgrade Reco <recoverym4n@gmail.com> - 2018-05-20 17:30 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-20 20:50 +0200
Re: making more room in root partition for distribution upgrade Reco <recoverym4n@gmail.com> - 2018-05-20 21:40 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-20 22:00 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-20 20:50 +0200
Re: making more room in root partition for distribution upgrade Richard Hector <richard@walnut.gen.nz> - 2018-05-21 07:20 +0200
Re: making more room in root partition for distribution upgrade songbird <songbird@anthive.com> - 2018-05-21 02:10 +0200
Re: making more room in root partition for distribution upgrade Andy Smith <andy@strugglers.net> - 2018-05-21 08:00 +0200
Re: making more room in root partition for distribution upgrade Curt <curty@free.fr> - 2018-05-21 10:30 +0200
Re: making more room in root partition for distribution upgrade Joe <joe@jretrading.com> - 2018-05-21 11:00 +0200
Re: making more room in root partition for distribution upgrade Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-21 17:00 +0200
Re: making more room in root partition for distribution upgrade Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-21 21:10 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-21 21:50 +0200
Re: making more room in root partition for distribution upgrade Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-21 22:20 +0200
Re: making more room in root partition for distribution upgrade Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-21 23:00 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-21 23:20 +0200
Re: making more room in root partition for distribution upgrade Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-22 00:20 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-22 20:30 +0200
Re: making more room in root partition for distribution upgrade Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-22 21:00 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-22 22:30 +0200
Re: making more room in root partition for distribution upgrade deloptes <deloptes@gmail.com> - 2018-05-22 23:30 +0200
Re: making more room in root partition for distribution upgrade Richard Hector <richard@walnut.gen.nz> - 2018-05-22 22:00 +0200
Re: making more room in root partition for distribution upgrade Jerome Kutche <n9lya@uronode.n9lya.ampr.org> - 2018-05-22 23:40 +0200
Re: making more room in root partition for distribution upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2018-05-23 03:20 +0200
Re: making more room in root partition for distribution upgrade Curt <curty@free.fr> - 2018-05-23 10:30 +0200
Re: making more room in root partition for distribution upgrade Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-05-21 14:20 +0200
Re: making more room in root partition for distribution upgrade David Baron <dbaron770@gmail.com> - 2018-05-21 15:10 +0200
Re: making more room in root partition for distribution upgrade David Wright <deblis@lionunicorn.co.uk> - 2018-05-21 16:00 +0200
Re: making more room in root partition for distribution upgrade Miroslav Skoric <skoric@eunet.rs> - 2018-05-25 11:40 +0200
Re: making more room in root partition for distribution upgrade David Wright <deblis@lionunicorn.co.uk> - 2018-05-25 22:50 +0200
Re: making more room in root partition for distribution upgrade Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-25 23:20 +0200
Page 1 of 3 [1] 2 3 Next page →
| From | Mark Copper <mcopper@straitcity.com> |
|---|---|
| Date | 2018-05-18 01:10 +0200 |
| Subject | making more room in root partition for distribution upgrade |
| Message-ID | <vQAc1-3uV-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
There was a day when a 10 gb partition seemed like plenty of space to leave for the system but now it's not. An upgrade to Stretch appears to need more. ~# fdisk -l Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0007c9ed Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 19531775 19529728 9.3G 83 Linux /dev/sda2 19533822 312580095 293046274 139.8G 5 Extended /dev/sda5 19533824 27578367 8044544 3.9G 82 Linux swap / Solaris /dev/sda6 27580416 312580095 284999680 135.9G 83 Linux $ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # / was on /dev/sda1 during installation UUID=f2959403-fb9c-4e56-adbf-e5b7c1f63dd8 / ext3 errors=remount-ro 0 1 # /home was on /dev/sda6 during installation UUID=274b606c-c556-47cb-8db3-2733b7adac3f /home ext3 defaults 0 2 # swap was on /dev/sda5 during installation UUID=5642269c-ada4-4466-a516-4a2360ee0ec1 none swap sw 0 0 This must be a FAQ. But there appear to be two ways forward. 1. Back-up /home, enlarge / partition, copy back-up back to new, smaller /home partition (because /home will then start on a different cylinder so data will be lost). or 2. Carve out a new partition for /usr at end of disk which will free up over 6 gb. What have other people done? Thanks.
[toc] | [next] | [standalone]
| From | bw <bwtnguy@yahoo.com> |
|---|---|
| Date | 2018-05-18 01:40 +0200 |
| Message-ID | <vQAF3-3Dv-5@gated-at.bofh.it> |
| In reply to | #195849 |
On Thu, 17 May 2018, Mark Copper wrote: > There was a day when a 10 gb partition seemed like plenty of space to leave > for the system but now it's not. An upgrade to Stretch appears to need more. > > ~# fdisk -l > > Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disklabel type: dos > Disk identifier: 0x0007c9ed > > Device Boot Start End Sectors Size Id Type > /dev/sda1 * 2048 19531775 19529728 9.3G 83 Linux > /dev/sda2 19533822 312580095 293046274 139.8G 5 Extended > /dev/sda5 19533824 27578367 8044544 3.9G 82 Linux swap / Solaris > /dev/sda6 27580416 312580095 284999680 135.9G 83 Linux > > $ cat /etc/fstab > # /etc/fstab: static file system information. > # > # Use 'blkid' to print the universally unique identifier for a > # device; this may be used with UUID= as a more robust way to name devices > # that works even if disks are added and removed. See fstab(5). > # > # <file system> <mount point> <type> <options> <dump> <pass> > proc /proc proc defaults 0 0 > # / was on /dev/sda1 during installation > UUID=f2959403-fb9c-4e56-adbf-e5b7c1f63dd8 / ext3 > errors=remount-ro 0 1 > # /home was on /dev/sda6 during installation > UUID=274b606c-c556-47cb-8db3-2733b7adac3f /home ext3 > defaults 0 2 > # swap was on /dev/sda5 during installation > UUID=5642269c-ada4-4466-a516-4a2360ee0ec1 none swap > sw 0 0 > > > This must be a FAQ. But there appear to be two ways forward. > > 1. Back-up /home, enlarge / partition, copy back-up back to new, smaller > /home partition (because /home will then start on a different cylinder so > data will be lost). > > or > > 2. Carve out a new partition for /usr at end of disk which will free up > over 6 gb. > > What have other people done? > > Thanks. > release notes on upgrading have some info about disk space. It's maybe /var/cache/apt/archives taking up all your space? I use 30 gb partitions usually and they very rarely get over 8-10 gigs. https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#sufficient-space good luck!
[toc] | [prev] | [next] | [standalone]
| From | Mark Copper <mcopper@straitcity.com> |
|---|---|
| Date | 2018-05-18 02:10 +0200 |
| Message-ID | <vQB85-42d-1@gated-at.bofh.it> |
| In reply to | #195854 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, May 17, 2018 at 6:32 PM, bw <bwtnguy@yahoo.com> wrote: > > > On Thu, 17 May 2018, Mark Copper wrote: > > > There was a day when a 10 gb partition seemed like plenty of space to > leave > > for the system but now it's not. An upgrade to Stretch appears to need > more. > > > > ~# fdisk -l > > > > Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors > > Units: sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes / 512 bytes > > I/O size (minimum/optimal): 512 bytes / 512 bytes > > Disklabel type: dos > > Disk identifier: 0x0007c9ed > > > > Device Boot Start End Sectors Size Id Type > > /dev/sda1 * 2048 19531775 19529728 9.3G 83 Linux > > /dev/sda2 19533822 312580095 293046274 139.8G 5 Extended > > /dev/sda5 19533824 27578367 8044544 3.9G 82 Linux swap / > Solaris > > /dev/sda6 27580416 312580095 284999680 135.9G 83 Linux > > > > $ cat /etc/fstab > > # /etc/fstab: static file system information. > > # > > # Use 'blkid' to print the universally unique identifier for a > > # device; this may be used with UUID= as a more robust way to name > devices > > # that works even if disks are added and removed. See fstab(5). > > # > > # <file system> <mount point> <type> <options> <dump> <pass> > > proc /proc proc defaults 0 0 > > # / was on /dev/sda1 during installation > > UUID=f2959403-fb9c-4e56-adbf-e5b7c1f63dd8 / ext3 > > errors=remount-ro 0 1 > > # /home was on /dev/sda6 during installation > > UUID=274b606c-c556-47cb-8db3-2733b7adac3f /home ext3 > > defaults 0 2 > > # swap was on /dev/sda5 during installation > > UUID=5642269c-ada4-4466-a516-4a2360ee0ec1 none swap > > sw 0 0 > > > > > > This must be a FAQ. But there appear to be two ways forward. > > > > 1. Back-up /home, enlarge / partition, copy back-up back to new, smaller > > /home partition (because /home will then start on a different cylinder so > > data will be lost). > > > > or > > > > 2. Carve out a new partition for /usr at end of disk which will free up > > over 6 gb. > > > > What have other people done? > > > > Thanks. > > > > release notes on upgrading have some info about disk space. It's maybe > /var/cache/apt/archives taking up all your space? I use 30 gb partitions > usually and they very rarely get over 8-10 gigs. > > https://www.debian.org/releases/stable/amd64/release- > notes/ch-upgrading.en.html#sufficient-space > > good luck! > > I think I'm good there: $ du -h /var ... 598M /var but $ du -h /usr ... 4.2G /usr/share 6.5G /usr Point well taken about removing packages though. Thanks
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2018-05-20 10:30 +0200 |
| Message-ID | <vRrT4-25a-3@gated-at.bofh.it> |
| In reply to | #195855 |
Le 18/05/2018 à 02:05, Mark Copper a écrit : >> >>> There was a day when a 10 gb partition seemed like plenty of space to leave >>> for the system but now it's not. An upgrade to Stretch appears to need more. How do you know ? >>> Device Boot Start End Sectors Size Id Type >>> /dev/sda1 * 2048 19531775 19529728 9.3G 83 Linux >>> /dev/sda2 19533822 312580095 293046274 139.8G 5 Extended >>> /dev/sda5 19533824 27578367 8044544 3.9G 82 Linux swap / Solaris >>> /dev/sda6 27580416 312580095 284999680 135.9G 83 Linux >>> >>> $ cat /etc/fstab >>> # / was on /dev/sda1 during installation >>> # /home was on /dev/sda6 during installation >>> # swap was on /dev/sda5 during installation >>> This must be a FAQ. But there appear to be two ways forward. >>> >>> 1. Back-up /home, enlarge / partition, copy back-up back to new, smaller >>> /home partition (because /home will then start on a different cylinder so >>> data will be lost). You will have to move/delete and re-create the swap too. Gparted allows to resize and move an unused partition. Better have a backup though. >>> 2. Carve out a new partition for /usr at end of disk which will free up >>> over 6 gb. The Debian initramfs supports a separate /usr since Jessie. > $ du -h /var > ... > 598M /var > > but > > $ du -h /usr > ... > 4.2G /usr/share > 6.5G /usr What about the rest ? How much free space is available ? Maybe the upgrade requires more space in order to download and store the new packages. Have you considered moving /var/cache/apt/archives to the /home partition (through a symlink or bind mount) so that downloaded packages do not use space in the / filesystem ?
[toc] | [prev] | [next] | [standalone]
| From | Mark Copper <mcopper@straitcity.com> |
|---|---|
| Date | 2018-05-21 18:20 +0200 |
| Message-ID | <vRVHr-3lz-5@gated-at.bofh.it> |
| In reply to | #195928 |
On Sun, May 20, 2018 at 3:19 AM, Pascal Hambourg <pascal@plouf.fr.eu.org> wrote: > Le 18/05/2018 à 02:05, Mark Copper a écrit : >>> >>> >>>> There was a day when a 10 gb partition seemed like plenty of space to >>>> leave >>>> for the system but now it's not. An upgrade to Stretch appears to need >>>> more. > > > How do you know ? I don't, actually. I'm reacting to warnings of limited space received when upgrading Jessie. And previously when upgrading from Wheezy IIRC. > >>>> Device Boot Start End Sectors Size Id Type >>>> /dev/sda1 * 2048 19531775 19529728 9.3G 83 Linux >>>> /dev/sda2 19533822 312580095 293046274 139.8G 5 Extended >>>> /dev/sda5 19533824 27578367 8044544 3.9G 82 Linux swap / >>>> Solaris >>>> /dev/sda6 27580416 312580095 284999680 135.9G 83 Linux >>>> >>>> $ cat /etc/fstab >>>> # / was on /dev/sda1 during installation >>>> # /home was on /dev/sda6 during installation >>>> # swap was on /dev/sda5 during installation > > >>>> This must be a FAQ. But there appear to be two ways forward. >>>> >>>> 1. Back-up /home, enlarge / partition, copy back-up back to new, smaller >>>> /home partition (because /home will then start on a different cylinder >>>> so >>>> data will be lost). > > > You will have to move/delete and re-create the swap too. > Gparted allows to resize and move an unused partition. Better have a backup > though. yes, if I understand, the file system is lost on any partition, primary or logical, whose first cylinder is changed. > >>>> 2. Carve out a new partition for /usr at end of disk which will free up >>>> over 6 gb. > > > The Debian initramfs supports a separate /usr since Jessie. Given the system as it currently exists, this seems the easiest way to go. (actually there are several boxes like this needing attention). > >> $ du -h /var >> ... >> 598M /var >> >> but >> >> $ du -h /usr >> ... >> 4.2G /usr/share >> 6.5G /usr > > > What about the rest ? How much free space is available ? > Maybe the upgrade requires more space in order to download and store the new > packages. Have you considered moving /var/cache/apt/archives to the /home > partition (through a symlink or bind mount) so that downloaded packages do > not use space in the / filesystem ? > Yes, should have included that: :~# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.1G 7.8G 870M 91% / udev 10M 0 10M 0% /dev tmpfs 402M 6.1M 396M 2% /run tmpfs 1005M 92K 1005M 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1005M 0 1005M 0% /sys/fs/cgroup /dev/sda6 134G 6.0G 121G 5% /home tmpfs 201M 8.0K 201M 1% /run/user/1000 /dev/sdb3 915G 5.8G 863G 1% /media/mark/d-live 9.4.0 gn amd64 /dev/sdb1 2.3G 2.3G 0 100% /media/mark/d-live 9.4.0 gn amd641 No, I had not considered playing with any part of /var. With /var taking less than 1 gb and /var/cache/apt/archives less than 1mb, /usr had seemed the elephant in the room. Might that be a way to go? I just need to get to Stretch for now. Thank you.
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2018-05-21 18:50 +0200 |
| Message-ID | <vRWau-3ww-11@gated-at.bofh.it> |
| In reply to | #195967 |
On 2018-05-21, Mark Copper <mcopper@straitcity.com> wrote: > > No, I had not considered playing with any part of /var. With /var > taking less than 1 gb and /var/cache/apt/archives less than 1mb, /usr > had seemed the elephant in the room. Might that be a way to go? I just > need to get to Stretch for now. There's actually advice in the release notes to that effect (along with other strategies for freeing or finding necessary space): https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#package-status A command can be run that supposedly will warn the constrained user if she hasn't enough room on disk for the upgrade (this after modifying the /etc/apt/sources.list file to point to Stretch and running apt(-get) update apt-get -o APT::Get::Trivial-Only=true dist-upgrade This failed to work as promised in my case (or I failed somehow somewhere along the line), and I ran out of room during my upgrade, but bungled through. I will spare the forum the gruesome details of my struggle. The release notes even give detailed instructions as to how you might mount bind (or is bind mount?) a usb key as a temporary /var/cache/apt/archives directory. Good luck. > Thank you. > > --
[toc] | [prev] | [next] | [standalone]
| From | Mark Copper <mcopper@straitcity.com> |
|---|---|
| Date | 2018-05-21 19:00 +0200 |
| Message-ID | <vRWk9-3A5-3@gated-at.bofh.it> |
| In reply to | #195968 |
> > The release notes even give detailed instructions as to how you might mount > bind (or is bind mount?) a usb key as a temporary /var/cache/apt/archives > directory. > That's an intriguing idea. I'll look. Thanks.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2018-05-21 19:30 +0200 |
| Message-ID | <vRWNc-40l-5@gated-at.bofh.it> |
| In reply to | #195969 |
Le 21/05/2018 à 18:52, Mark Copper a écrit : >> >> The release notes even give detailed instructions as to how you might mount >> bind (or is bind mount?) a usb key as a temporary /var/cache/apt/archives >> directory. > > That's an intriguing idea. I'll look. Thanks. There is plenty of free space in /home, so no need to use a (slow and unreliable) USB drive.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2018-05-21 19:30 +0200 |
| Message-ID | <vRWNc-40l-3@gated-at.bofh.it> |
| In reply to | #195967 |
Le 21/05/2018 à 18:14, Mark Copper a écrit : > On Sun, May 20, 2018 at 3:19 AM, Pascal Hambourg <pascal@plouf.fr.eu.org> wrote: >> Le 18/05/2018 à 02:05, Mark Copper a écrit : >> >> You will have to move/delete and re-create the swap too. >> Gparted allows to resize and move an unused partition. Better have a backup >> though. > > yes, if I understand, the file system is lost on any partition, > primary or logical, whose first cylinder is changed. Not with Gparted. Gparted moves the data to the new location of the partition. But things can go wrong during the operation (power failure, system crash...) so better keep a backup. Note : cylinders are deprecated. LBA is used instead. >>> 6.5G /usr >> >> What about the rest ? How much free space is available ? (...) > Yes, should have included that: > > :~# df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sda1 9.1G 7.8G 870M 91% / the other filesystems are of no interest. I meant the rest of the / filesystem. > No, I had not considered playing with any part of /var. With /var > taking less than 1 gb and /var/cache/apt/archives less than 1mb /var/cache/apt/archives will temporarily grow a lot during the upgrade, as it will contain all the dowloaded *.deb files. When apt-get says "Need to get X MB of archives", it means that these X MB will go into /var/cache/apt/archives.
[toc] | [prev] | [next] | [standalone]
| From | Mark Copper <mcopper@straitcity.com> |
|---|---|
| Date | 2018-05-25 02:30 +0200 |
| Message-ID | <vT8Mh-7W3-5@gated-at.bofh.it> |
| In reply to | #195972 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, May 21, 2018 at 12:23 PM, Pascal Hambourg <pascal@plouf.fr.eu.org> wrote: Le 21/05/2018 à 18:14, Mark Copper a écrit : > >> On Sun, May 20, 2018 at 3:19 AM, Pascal Hambourg <pascal@plouf.fr.eu.org> >> wrote: >> >>> Le 18/05/2018 à 02:05, Mark Copper a écrit : >>> >>> You will have to move/delete and re-create the swap too. >>> Gparted allows to resize and move an unused partition. Better have a >>> backup >>> though. >>> >> >> yes, if I understand, the file system is lost on any partition, >> primary or logical, whose first cylinder is changed. >> > > Not with Gparted. Gparted moves the data to the new location of the > partition. But things can go wrong during the operation (power failure, > system crash...) so better keep a backup Ah, gparted made it all very easy. (One little bump: some bug requiring a little empty space separating logical partitions). "/" enlarged, stretch installed with room to, er, stretch! Thanks.
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2018-05-25 20:30 +0200 |
| Message-ID | <vTpDr-1mN-3@gated-at.bofh.it> |
| In reply to | #196058 |
Le 25/05/2018 à 02:23, Mark Copper a écrit : > > One little bump: some bug requiring a > little empty space separating logical partitions) It's not a bug, it's a feature of the extended partition layout. In short, each logical partition inside an extended partition must be preceded by an extended partition table occupying one sector. Due to current partition alignment practice, the gap between logical partitions is 1 MiB. If you don't want to waste that space, get rid of logical partitions and use GPT.
[toc] | [prev] | [next] | [standalone]
| From | Abdullah Ramazanoğlu <ar018@yahoo.com> |
|---|---|
| Date | 2018-05-18 03:10 +0200 |
| Message-ID | <vQC4a-4z1-3@gated-at.bofh.it> |
| In reply to | #195849 |
On Thu, 17 May 2018 18:06:46 -0500 Mark Copper said: [ ---8<--- ] > This must be a FAQ. But there appear to be two ways forward. > > 1. Back-up /home, enlarge / partition, copy back-up back to new, smaller > /home partition (because /home will then start on a different cylinder so > data will be lost). > > or > > 2. Carve out a new partition for /usr at end of disk which will free up > over 6 gb. I had the same problem a while ago and enlarged my root partition from 10G to 40G. I guess it was a bit overkill, as my root partition is 8,5G now. So I think 20 to 30 G depending on usage specifics should be fine. I would recommend against (2) the reason being the more partitioned your disk layout, the less efficient use of disk space (the more pooled the more efficient use of space). So, your actual disk layout is quite sensible IMO, and I would have stuck (1). But then, once /home is backed up, there is no more need to "enlarge" the root partition (as in resize2fs, if you meant that). I would have simply re-partitioned the disk with the same layout as it is now (except different partition sizes), do a fresh install, and then restore /home to its new partition. Regards -- Abdullah Ramazanoğlu
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2018-05-18 03:30 +0200 |
| Message-ID | <vQCnv-4EP-3@gated-at.bofh.it> |
| In reply to | #195849 |
Hi, On Thu, May 17, 2018 at 06:06:46PM -0500, Mark Copper wrote: [sda1 root partition got too small; extended partition on sda2 fills remainder of disk] > This must be a FAQ. But there appear to be two ways forward. > > 1. Back-up /home, enlarge / partition, copy back-up back to new, smaller > /home partition (because /home will then start on a different cylinder so > data will be lost). > > or > > 2. Carve out a new partition for /usr at end of disk which will free up > over 6 gb. > > What have other people done? If using multiple partitions per disk, consider using LVM in future as otherwise this sort of thing nearly always becomes a chore. Personally in your situation I'd probably back up /home and then turn /home's device (/dev/sda6) into an LVM PV, then create LVs for /home, /var and whatever else takes up significant space before copying the /home data back in. My reasoning for this is that as you do all of this work as root, everything in /home is basically just data that is not required for managing the system. Therefore the procedure is simpler and less error-prone, in my opinion. It avoids messing about with the root filesystem, and any kind of partition resizing. When using LVM I don't tend to split up / and /usr. It is perfectly possible to have / in LVM; modern grub will cope. But I tend to find that after one has put all of the larger subdirectories into their own LV, the combined space usage of /-and-/usr is fairly small and mostly static. So for simplicity's sake I just rather pick a reasonable size for / and keep it as a real partition with /usr inside it. I don't generally see the point of putting swap into LVM either, again because the size of it rarely changes. Should you find you do require more swap it can always be added later as devices or swapfile. As you can see I greatly value simplicity, which for me is a hard-won lesson in the sysadmin trenches. Other people like a more exciting life, so each to their own. :) Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | Rick Thomas <rbthomas@pobox.com> |
|---|---|
| Date | 2018-05-18 13:10 +0200 |
| Message-ID | <vQLqN-1LO-5@gated-at.bofh.it> |
| In reply to | #195857 |
On May 17, 2018, at 6:19 PM, Andy Smith <andy@strugglers.net> wrote: > If using multiple partitions per disk, consider using LVM in future > as otherwise this sort of thing nearly always becomes a chore. I strongly second the recommendation to use LVM wherever possible. It greatly simplifies the process of re-sizing partitions as usage changes. Contrary to Andy’s recommendation, though, I would also put swap on LVM — if only just to simplify things when I do find myself needing to adjust it — simplifying a rare procedure is nevertheless a simplification and worth having. Secondly, I heartily recommend the GRML live system for when you need to do this kind of thing. It’s a fully fledged live Debian derived OS, designed to have all the sys-admin tools you need, on a single USB or DVD. Hope it helps! Rick
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2018-05-18 14:10 +0200 |
| Message-ID | <vQMmR-2nk-5@gated-at.bofh.it> |
| In reply to | #195872 |
Hello, On Fri, May 18, 2018 at 04:00:45AM -0700, Rick Thomas wrote: > Contrary to Andy’s recommendation, though, I would also > put swap on LVM — if only just to simplify things when I do find > myself needing to adjust it Well, OK. But… Should I need more swap then I don't really find adding an additional swap device with: # lvcreate -L1g -n /dev/myvg/more-swap-vicar # swapon /dev/myvg/more-swap-vicar # echo '/dev/myvg/more-swap-vicar swap swap defaults 0 0' >> /etc/fstab any more difficult than your suggestion of resizing a swap that was already in LVM: # swapoff -a # lvresize -L2g /dev/myvg/my-only-swap # mkswap /dev/myvg/my-only-swap # swapon -a Yet in the overwhelmingly common case for me, I never adjust the size of swap so having it outside of LVM means it works even if I somehow break LVM. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2018-05-18 05:00 +0200 |
| Message-ID | <vQDMB-5rq-1@gated-at.bofh.it> |
| In reply to | #195849 |
Mark Copper composed on 2018-05-17 18:06 (UTC-0500): > There was a day when a 10 gb partition seemed like plenty of space to leave > for the system but now it's not. An upgrade to Stretch appears to need more. ... > What have other people done? My largest Stretch root partition is 5.6GB. One or more of my 32 bit Stretch installations may be on 4.8GB. All have separate partitions for /home and /usr/local, none /opt or /usr. All are either EXT3 or EXT4. None have Cinnamon, XFCE, Gnome, Mate, KDE or LibreOffice. Most have only IceWM and TDE. Nothing stays in apt's cache for long, but I do have more than two installed kernels on many of them. Also, all are kept svelte by APT::Install-Recommends "false";. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | ntrfug <ntrfug@cox.net> |
|---|---|
| Date | 2018-05-19 16:30 +0200 |
| Message-ID | <vRb1T-rm-1@gated-at.bofh.it> |
| In reply to | #195849 |
On Thu, 17 May 2018 18:06:46 -0500 Mark Copper <mcopper@straitcity.com> wrote: > This must be a FAQ. But there appear to be two ways forward. > > 1. Back-up /home, enlarge / partition, copy back-up back to new, > smaller /home partition (because /home will then start on a different > cylinder so data will be lost). > > or > > 2. Carve out a new partition for /usr at end of disk which will free > up over 6 gb. > > What have other people done? > > Thanks. More than 20 years ago I began saving personal files to a different partition than the OS. I've used this system for Windows (when I started) and for more flavors of Linux than I can remember. I did this so I could wipe the root partition and reinstall without destroying my personal files. I call it "files" and mount it on /home/ntrfug/Documents at boot. I also have a 100 Gb partition for "music", mounted at boot to /home/ntrfug/Music. Everything else goes on single 22 Gb partition, now labeled "Stretch" (49% occupied). I use KDE with a fair but not extensive portfolio of software, but which include LyX, which requires LaTeX and TeX (that's a lot of dependency). I backup the root partition before I reinstall, and after installation move settings for individual applications to the new home directory. For example I started using sylpheed for email when accounts and preferences were saved in regular text files. Later it morphed to claws-mail and migrated to xml preferences that I could not re-create to save my life. Fortunately I just moved the /home/ntrfug/.config/claws-mail directory to my new system and it came up with all my preferences and accounts the first time I started. (I save my email folders in /home/ntrfug/files/Mail). I use VirtualBox, and virtual machines live in /home/ntrfug/files/virtualbox.
[toc] | [prev] | [next] | [standalone]
| From | Charlie S <taoquester@gmail.com> |
|---|---|
| Date | 2018-05-20 08:00 +0200 |
| Message-ID | <vRpxT-tt-5@gated-at.bofh.it> |
| In reply to | #195902 |
On Sat, 19 May 2018 09:16:43 -0500 ntrfug sent: > More than 20 years ago I began saving personal files to a different > partition than the OS. > > I've used this system for Windows (when I started) and for more > flavors of Linux than I can remember. I did this so I could wipe the > root partition and reinstall without destroying my personal files. > > I call it "files" and mount it on /home/ntrfug/Documents at boot. <snip> After contemplation, my reply is: I thought that's what everyone did? Have a root, a home, a usr, a var, a tmp, graphics, etc etc.. partition. If ever there is a problem with the O/S and in the event it needs reinstallation. Install what O/S is desired and allow all the other partitions to be used, but not formatted. I must admit I thought this was the norm, even with windows? Though I did read somewhere that if there is a separate /usr partition that some things, with systemd, like my backlight on the monitor receives an error message, which mine does? Once the O/S is installed with all that is used, the configuration files from home just kick in automagically? Or so it has been for myself. Charlie -- Registered Linux User:- 329524 *********************************************** A free society is a place where it is safe to be unpopular. --Adlai Stevenson *********************************************** Debian GNU/Linux - Magic indeed. -----------------------------------------------------
[toc] | [prev] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2018-05-20 14:40 +0200 |
| Message-ID | <vRvN0-4pJ-9@gated-at.bofh.it> |
| In reply to | #195926 |
Charlie S wrote: > On Sat, 19 May 2018 09:16:43 -0500 ntrfug sent: > >> More than 20 years ago I began saving personal files to a different >> partition than the OS. >> >> I've used this system for Windows (when I started) and for more >> flavors of Linux than I can remember. I did this so I could wipe the >> root partition and reinstall without destroying my personal files. >> >> I call it "files" and mount it on /home/ntrfug/Documents at boot. > ><snip> > > After contemplation, my reply is: > > I thought that's what everyone did? > > Have a root, a home, a usr, a var, a tmp, graphics, etc etc.. partition. > > If ever there is a problem with the O/S and in the event it needs > reinstallation. Install what O/S is desired and allow all the other > partitions to be used, but not formatted. ... in my last system i had many different partitions like that but with the new system i decided that was wasting too much space and so with the new one i've gone to keeping everything in one partition per version i'm booting. that way i'm not wasting much space. i have four partitions, boot/efi, root for testing, root for stable and then swap. i'm not doing RAID or LVM or encryption as nothing i do is that critical (i do have a separate backup device). i think the main point to consider though is what the system is being used for. in a production system where you may have large areas of data, pictures, etc. which are apart from user files and the OS then it makes sense to have things split apart but for most people doing things on a home system maybe you don't need that complexity? for me the gain in space moving to the new system was great. if i need to reorganize later chances are pretty good i'll just buy an additional SSD as capacity should continue to improve for about the same price. i may not really have to buy a new system again until this one burns out completely. the SSDs can be leapfrogged easily enough as time goes on if i run out of SATA connections or slots. songbird
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2018-05-20 15:10 +0200 |
| Message-ID | <vRwg2-4Q9-7@gated-at.bofh.it> |
| In reply to | #195930 |
Le 20/05/2018 à 14:33, songbird a écrit : > > in my last system i had many different partitions like that but > with the new system i decided that was wasting too much space and Then LVM is your friend. You can create as many logical volumes as you like with minimal sizes and easily extend them when needed. This way you don't waste space in overprovisioning.
[toc] | [prev] | [next] | [standalone]
Page 1 of 3 [1] 2 3 Next page →
Back to top | Article view | linux.debian.user
csiph-web