[opensuse] Partitioning Recommendations on New Install
Hi guys, I know this has been asked many times, and probably by me more than once, but here goes again. I finally got an SSD which I'd like to install on my Linux box. Yea! Starting off with a new drive I have the luxury to start fresh, i.e. place grub where I want. But, I liked to maintain my existing installs as bootable at least for a while while I get the new install set up properly. But new install on a new drive gives me that chance to re-think my past partitioning setup and bring it up to current thinking. I'm on Leap 42.3 and I'd like to stay with Leap (not TW), 42.3 has been very stable and to my liking. Currently I have 2 physical drives, sda with Grub in MBR (I think), sda1 is swap, sda5 and sda6 are installation drives (extended), and sda7 is basically storage. sdb is music, nothing else. What I've done in the past is to do / installs of new releases in the older of the two sda6 or sda7, alternating between keeping the newest, and installing the new release on the older of the two. No separate /home, all each in /. That way I could keep my most current release working and install the new one to play with and migrate to when ready, basically copy /home over the the new install. I have had problems with Grub finding the older install from time to time, but mostly this worked. But, openSuse has moved forward and seems there's a better way to upgrade now. My new SSD is a 120GB Kingston. I don't think I could do the 2 separate partition installs on this as my current partition is 100GB with about 50GB free. I don't want to limit my working space too much. The 120GB drive would give me about 50 or 55GB space for each of the two and I feel that's too limiting. I do plan on keeping teh current sda for large files and other storage to save space on the SSD. So to get down to it, what is the recommended way to install Leap 15 on this new drive? I'd like to keep boot access to at least 42.3. I'm not sure how that will work with Grub on MBR on sda. Should Grub go on the new SSD, and in MBR or other? And what's the recommended partitioning scheme so that I can upgrade or clean install new releases going forward? Install is for a basic desktop, no email server or web server. Not major use anyway. Intel i5 4GB ram Currently have Leap 42.3 and oS 13.2 but don't' need that. Not sure you need this but here's my current partitioning setup. Other than swap, all are Ext4 except 42.3 which is BtrFS. linux-di48:/home/jim # fdisk -l Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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: 0x0003f497 Device Boot Start End Sectors Size Id Type /dev/sda1 2048 8386559 8384512 4G 82 Linux swap / Solaris /dev/sda2 8386560 8787967 401408 196M 83 Linux /dev/sda3 * 8787968 976773119 967985152 461.6G f W95 Ext'd (LBA) /dev/sda5 8790016 218499071 209709056 100G 83 Linux /dev/sda6 218501120 428212223 209711104 100G 83 Linux /dev/sda7 428214272 976752639 548538368 261.6G 83 Linux Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 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: 0x0009f628 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 629153791 629151744 300G 83 Linux /dev/sdb2 629153792 2097172479 1468018688 700G 83 Linux Many thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/02/2019 03.10, Jim Flanagan wrote:
Hi guys,
I know this has been asked many times, and probably by me more than once, but here goes again. I finally got an SSD which I'd like to install on my Linux box. Yea! Starting off with a new drive I have the luxury to start fresh, i.e. place grub where I want. But, I liked to maintain my existing installs as bootable at least for a while while I get the new install set up properly. But new install on a new drive gives me that chance to re-think my past partitioning setup and bring it up to current thinking.
I'm on Leap 42.3 and I'd like to stay with Leap (not TW), 42.3 has been very stable and to my liking. Currently I have 2 physical drives, sda with Grub in MBR (I think), sda1 is swap, sda5 and sda6 are installation drives (extended), and sda7 is basically storage. sdb is music, nothing else. What I've done in the past is to do / installs of new releases in the older of the two sda6 or sda7, alternating between keeping the newest, and installing the new release on the older of the two. No separate /home, all each in /. That way I could keep my most current release working and install the new one to play with and migrate to when ready, basically copy /home over the the new install. I have had problems with Grub finding the older install from time to time, but mostly this worked. But, openSuse has moved forward and seems there's a better way to upgrade now.
My new SSD is a 120GB Kingston. I don't think I could do the 2 separate partition installs on this as my current partition is 100GB with about 50GB free. I don't want to limit my working space too much. The 120GB drive would give me about 50 or 55GB space for each of the two and I feel that's too limiting. I do plan on keeping teh current sda for large files and other storage to save space on the SSD.
Pity you didn't get a 250 GB, to do it the same way.
So to get down to it, what is the recommended way to install Leap 15 on this new drive? I'd like to keep boot access to at least 42.3. I'm not sure how that will work with Grub on MBR on sda. Should Grub go on the new SSD, and in MBR or other? And what's the recommended partitioning scheme so that I can upgrade or clean install new releases going forward?
There is no "recommended way". We can each tell how we would do it :-)
Install is for a basic desktop, no email server or web server. Not major use anyway. Intel i5 4GB ram Currently have Leap 42.3 and oS 13.2 but don't' need that.
Not sure you need this but here's my current partitioning setup. Other than swap, all are Ext4 except 42.3 which is BtrFS.
A 100 GB "/" btrfs can be changed to 50 GB "/" on ext4, so you could have two on ssd. Your call, not mine. I assume your computer is old, and uses BIOS, not UEFI. Assuming you want to install fresh, I would first create a GPT partition table on the SSD, then using the installer let it basically do, which will be create a very small bios partition and then the rest. I would change the rest (expert mode) as: one "/" of 50 GB ext4 mounted by label. one "/other" of 50 GB ext4 mounted by label. one swap of the rest, mounted by label. Later, after system install, format current sda5 or sdda6 as separate home. Or perhaps, join both into one. On boot setup, make sure that grub is *not* installed on the MBR, but on the partition and that one is marked bootable. After installation you can install another system on the /other partition. You change boot to one or the other "permanently" simply by changing the boot mark. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Wed, 20 Feb 2019, Carlos E. R. wrote:
There is no "recommended way". We can each tell how we would do it :-)
Assuming you want to install fresh, I would first create a GPT partition table on the SSD, then using the installer let it basically do, which will be create a very small bios partition ...
What size would you choose for this very small bios partition? Roger -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/02/2019 11.16, Roger Price wrote:
On Wed, 20 Feb 2019, Carlos E. R. wrote:
There is no "recommended way". We can each tell how we would do it :-)
Assuming you want to install fresh, I would first create a GPT partition table on the SSD, then using the installer let it basically do, which will be create a very small bios partition ...
What size would you choose for this very small bios partition?
Yast will say. Mine is 7 M -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2/20/19 3:54 AM, Carlos E. R. wrote:
On 20/02/2019 03.10, Jim Flanagan wrote:
Hi guys,
My new SSD is a 120GB Kingston. I don't think I could do the 2 separate partition installs on this as my current partition is 100GB with about 50GB free. I don't want to limit my working space too much. The 120GB drive would give me about 50 or 55GB space for each of the two and I feel that's too limiting. I do plan on keeping teh current sda for large files and other storage to save space on the SSD.
Pity you didn't get a 250 GB, to do it the same way.
It was an impulse buy. They were $17 on Amazon, I bought 3. One intended for this box and the others for 2 different Windows boxes. I may put two of them in this box for the purpose as originally outlined going forward, but for now will start with only one.
A 100 GB "/" btrfs can be changed to 50 GB "/" on ext4, so you could have two on ssd. Your call, not mine.
I assume your computer is old, and uses BIOS, not UEFI.
Yes, meant to say, BIOS.
Assuming you want to install fresh, I would first create a GPT partition table on the SSD, then using the installer let it basically do, which will be create a very small bios partition and then the rest. I would change the rest (expert mode) as:
Will the Yast installer set up the GPT partition or do I need to do that first with another utility? (I've never used GPT before but sounds fun). And by letting the installer create a very small bios partition do you mean /boot partition?
one "/" of 50 GB ext4 mounted by label.
one "/other" of 50 GB ext4 mounted by label.
one swap of the rest, mounted by label.
I take it you don't like BtrFS. Do you put /swap on an SSD? I've read that very heavy writes on an SSD will wear it out prematurely. My system rarely uses swap, unless Firefox takes of the whole machine which happened recently. (Read you had this issue in another thread). And how do I select mounted by label? I don't recall seeing that option on install before, but understand why its needed.
Later, after system install, format current sda5 or sdda6 as separate home. Or perhaps, join both into one.
On boot setup, make sure that grub is *not* installed on the MBR, but on the partition and that one is marked bootable.
So on this new install, I'll set up a new GPT partition. How will that interact, if at all, with the existing MBR on current sda? I realize I won't need that one anymore after all set up. Regarding /home, does should that be on SSD or HDD? Does a sperate /home really work well? I've read that upgrading a systme with seperate /home makes it easier, but sometimes old /home stuff caused trouble. Any experience with this?
After installation you can install another system on the /other partition. You change boot to one or the other "permanently" simply by changing the boot mark.
Understood. Many thanks, Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/02/2019 17.50, Jim Flanagan wrote:
On 2/20/19 3:54 AM, Carlos E. R. wrote:
On 20/02/2019 03.10, Jim Flanagan wrote:
Hi guys,
My new SSD is a 120GB Kingston. I don't think I could do the 2 separate partition installs on this as my current partition is 100GB with about 50GB free. I don't want to limit my working space too much. The 120GB drive would give me about 50 or 55GB space for each of the two and I feel that's too limiting. I do plan on keeping teh current sda for large files and other storage to save space on the SSD.
Pity you didn't get a 250 GB, to do it the same way.
It was an impulse buy. They were $17 on Amazon, I bought 3. One intended for this box and the others for 2 different Windows boxes. I may put two of them in this box for the purpose as originally outlined going forward, but for now will start with only one.
That's a very nice price :-)
A 100 GB "/" btrfs can be changed to 50 GB "/" on ext4, so you could have two on ssd. Your call, not mine.
I assume your computer is old, and uses BIOS, not UEFI.
Yes, meant to say, BIOS.
Ok
Assuming you want to install fresh, I would first create a GPT partition table on the SSD, then using the installer let it basically do, which will be create a very small bios partition and then the rest. I would change the rest (expert mode) as:
Will the Yast installer set up the GPT partition or do I need to do that first with another utility?
I don't remember :-) Probably, but to make sure, just create the partition table with gparted.
(I've never used GPT before but sounds fun). And by letting the installer create a very small bios partition do you mean /boot partition?
Nope. It is not mounted and will be left unused. It is only used by grub if it is installed in MBR (with raw data), because not everything fits there on GPT partitions. YaST will insist on it. About 8 MB, so it doesn't matter.
one "/" of 50 GB ext4 mounted by label.
one "/other" of 50 GB ext4 mounted by label.
one swap of the rest, mounted by label.
I take it you don't like BtrFS.
No, but I was trying to put two root partitions there, for two installs; I considered that more important than your choice of filesystem ;-) If you count on using another disk, then use 100GB for root as btrfs and the rest for swap,
Do you put /swap on an SSD? I've read that very heavy writes on an SSD will wear it out prematurely. My system rarely uses swap, unless Firefox takes of the whole machine which happened recently. (Read you had this issue in another thread).
Yes, it wears faster, but... so what? :-) With current technology that will not matter much. And it runs so much faster that it does make a difference, /if/ swap is used.
And how do I select mounted by label? I don't recall seeing that option on install before, but understand why its needed.
Get to this view: Partitioner: computer hard disks sda sda1 <====== Click on the edit button. Then on fstab options. There you will see mount by ... and another box to enter the label. You can also go to computer hard disks raid volume management nfs btrfs device graphs installation summary settings <==== There you can set the default mount by mode. Doing that the first thing, any new partition will be done that way.
Later, after system install, format current sda5 or sdda6 as separate home. Or perhaps, join both into one.
On boot setup, make sure that grub is *not* installed on the MBR, but on the partition and that one is marked bootable.
So on this new install, I'll set up a new GPT partition. How will that interact, if at all, with the existing MBR on current sda? I realize I won't need that one anymore after all set up.
It doesn't interact. Ah, I forgot: on the BIOS you will have it to boot from 120 GB disk.
Regarding /home, does should that be on SSD or HDD? Does a sperate /home really work well? I've read that upgrading a systme with seperate /home makes it easier, but sometimes old /home stuff caused trouble. Any experience with this?
If you have space, home on ssd is certainly faster. On my laptop everything is on the single SSD, but on the desktop home is on rotating rust, simply because it is much bigger and I handle some big files. Yes, a separate home works very well. In the cases where old stuff makes issues, you only have to delete some directories or files with a dot prepended. Another option is to have /home not separate, and instead have ~/Documents point to a /data partition elsewhere. This allows each operating system to have its own home with configs, while your data is elsewhere with more space. Well, Documents and whatever you use, like Photos, videos.... maybe Mail. This would have most of the pletora of small files used by the desktop on the faster SSD disk, too. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2/20/19 12:19 PM, Carlos E. R. wrote:
On 20/02/2019 17.50, Jim Flanagan wrote:
On 2/20/19 3:54 AM, Carlos E. R. wrote:
On 20/02/2019 03.10, Jim Flanagan wrote:
Hi guys,
My new SSD is a 120GB Kingston. I don't think I could do the 2 separate partition installs on this as my current partition is 100GB with about 50GB free. I don't want to limit my working space too much. The 120GB drive would give me about 50 or 55GB space for each of the two and I feel that's too limiting. I do plan on keeping teh current sda for large files and other storage to save space on the SSD.
Pity you didn't get a 250 GB, to do it the same way.
It was an impulse buy. They were $17 on Amazon, I bought 3. One intended for this box and the others for 2 different Windows boxes. I may put two of them in this box for the purpose as originally outlined going forward, but for now will start with only one.
That's a very nice price :-)
I assume your computer is old, and uses BIOS, not UEFI.
Yes, meant to say, BIOS.
Ok
Assuming you want to install fresh, I would first create a GPT partition table on the SSD, then using the installer let it basically do, which will be create a very small bios partition and then the rest. I would change the rest (expert mode) as:
Will the Yast installer set up the GPT partition or do I need to do that first with another utility?
I don't remember :-)
Probably, but to make sure, just create the partition table with gparted.
(I've never used GPT before but sounds fun). And by letting the installer create a very small bios partition do you mean /boot partition?
Nope. It is not mounted and will be left unused. It is only used by grub if it is installed in MBR (with raw data), because not everything fits there on GPT partitions.
YaST will insist on it. About 8 MB, so it doesn't matter.
This install went pretty well. The installer didn't detect or offer to install on the new sdc SSD drive. So I created a GPT boot partition on it with Gparted. Then re-booted back into the installer. It then recognized the drive and offered that as an install. I went with the default offer of 40GB BtrFS as / and the rest at XFS for /home. I did let it set up a 8mb /boot partition. Installer insisted on using the /swap on the old platter drive. I could not figure out how to make a new swap first on the SSD, or at least after the /boot, so I set it up last as sdc4 (after /boot, /, and /home). I gotta say, this drive is fast! I have an SSD notebook and am used to that, but having the frame of reference on my old install, this one is like day vs night! Grub did make an entry for my 42.3 install, but when I select that it can't find the ramdrive. Might be due to me moving the Sata cables before install to connect the new SSD drive. Not sure. But the new install is great so far. Gonna migrate over soon. Got the old platters set to mount by user so I access to them. Had a little trouble getting my music streamer installed but that's working now too (LMS). Thanks for the good help. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-02-25 5:40 p.m., Jim Flanagan wrote:
This install went pretty well. The installer didn't detect or offer to install on the new sdc SSD drive. So I created a GPT boot partition on it with Gparted. [...] I could not figure out how to make a new swap first on the SSD, or at least after the /boot, so I set it up last as sdc4 (after /boot, /, and /home).
I have no doubt that when you need to get into swapping/paging, having a SWAP on the SSD will be of great benefit. Given my druthers I'd spend more on not swapping/paging :-) I realise that most laptops are ;closed boxes' and you can't upgrade memory (much) and many desktops are also max-memory limited, if not by slots then by the number of address wires on the motherboard. Of course that may be a 'throw more money at it" problem. And so the basement accumulates old chassis and motherboards and even laptops. Oh, and drives. You might joke about driving though the old township and seeing houses with a couple of cars rusting away on the lot, but this is modern equivalent: old computers rotting away in the basement ... Hm, sorry, back on subject.... Despite my preference for LVM I make a point of using Gparted to set up my primary drive with a SWAP area that is a primary partition _before_ the install. The installer is smart enough to recognise this. If I need it, I can always set up a LVM V as another swap area. Actually, IIR, very late model UNIX SVR4 and Linux you can, even if you don't use LVM, dynamically create more swap by using the existing file system and creating a "swap FILE". <quote src="https://opensource.com/article/18/9/swap-space-linux-systems"> Types of Linux swap Linux provides for two types of swap space. By default, most Linux installations create a swap partition, but it is also possible to use a specially configured file as a swap file. A swap partition is just what its name implies—a standard disk partition that is designated as swap space by the mkswap command. A swap file can be used if there is no free disk space in which to create a new swap partition or space in a volume group where a logical volume can be created for swap space. This is just a regular file that is created and preallocated to a specified size. </quote> It is not as ... well .. 'efficient' as a primary partition or a LV. I love to avoid SWAP. But sometimes it ends up being necessary. Sadly some application, especially ones that do 'gratuitous imagery' demand more memory and hence get into swapping. I find Dolphin is one of these. If I have it viewing a directory of my photographs the thumbnails of the JPGs and the JPGS embedded in the RAWs demand so much space that the machine gets into swap. I kill dolphin and the swap gets freed. maybe. Sometimes SWAP doesn't get freed. In that case I create a SWAP LV, enable that, disable the old SWAP, then reverse the procedure. It flushed out redundant SWAP area and compresses it nicely. Summary: (a) when setting up your primary disk use GParted/fdisk to create a SWAP area as a primary partition before doing the install. (b) if and only if needed to deal with overflow or clean-up create additional SWAP as a LV or file but purely as a temporary measure. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/02/2019 23.40, Jim Flanagan wrote:
On 2/20/19 12:19 PM, Carlos E. R. wrote:
This install went pretty well. The installer didn't detect or offer to install on the new sdc SSD drive. So I created a GPT boot partition on it with Gparted. Then re-booted back into the installer. It then recognized the drive and offered that as an install. I went with the default offer of 40GB BtrFS as / and the rest at XFS for /home. I did let it set up a 8mb /boot partition. Installer insisted on using the /swap on the old platter drive. I could not figure out how to make a new swap first on the SSD, or at least after the /boot, so I set it up last as sdc4 (after /boot, /, and /home).
As it saw another disk that had swap, it saw no need to create another one. Well, the trick is going into expert mode and doing it your way. Delete home, create swap, add home again. It doesn't matter the position on an SSD disk. In a rotating disk, the faster area is about 1/3 in, not at the start - or so I found out when I tested. Another new test may find different again. I doubt it created an "8mb /boot partition", though, but an "8mb BIOS partition". I suspect a 40 GB btrfs root partition is too small. Be careful with space before upgrades.
I gotta say, this drive is fast! I have an SSD notebook and am used to that, but having the frame of reference on my old install, this one is like day vs night!
True.
Grub did make an entry for my 42.3 install, but when I select that it can't find the ramdrive. Might be due to me moving the Sata cables before install to connect the new SSD drive. Not sure.
Maybe not using uuid.
But the new install is great so far. Gonna migrate over soon. Got the old platters set to mount by user so I access to them. Had a little trouble getting my music streamer installed but that's working now too (LMS).
Thanks for the good help.
Welcome :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-02-19 9:10 p.m., Jim Flanagan wrote:
Yea! Starting off with a new drive I have the luxury to start fresh, i.e. place grub where I want. But, I liked to maintain my existing installs as bootable at least for a while while I get the new install set up properly. But new install on a new drive gives me that chance to re-think my past partitioning setup and bring it up to current thinking.
I've said it before and I'll say it again. The use of LVM gives you flexibility over such decisions and you have what is sometimes termed "deferred design". You don't have to commit to hard boundaries and you can 'repartition' (aka grow or shrink (if the FS permits) on a live system. More to the point: you can set up the LVM on the new drive and then as you migrate across, convert the old partition to LVM extents as well and add to the pool. That gives you the opportunity to do things like mirroring, striping and more :-) Over the years I've hit many "I wonder if I could" situations and found that LVM is immensely capable, even for doing some seemingly ridiculous things. (Like convincing the system you have more space available than actually exists, as sort of 'virtual memory' for disk space.) But if your issue is migrating an indeterminate /home .... well yes, I've done a LOT of shuffling like that. And now I have *everything* (except /boot) under LVM, migrating from one drive to another, one file system to another, in real time. without taking the system down, is a LVM function -- no need for 'rsync' and trying to remember to options :-) -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/02/2019 15.31, Anton Aylward wrote:
On 2019-02-19 9:10 p.m., Jim Flanagan wrote:
Yea! Starting off with a new drive I have the luxury to start fresh, i.e. place grub where I want. But, I liked to maintain my existing installs as bootable at least for a while while I get the new install set up properly. But new install on a new drive gives me that chance to re-think my past partitioning setup and bring it up to current thinking.
I've said it before and I'll say it again. The use of LVM gives you flexibility over such decisions and you have what is sometimes termed "deferred design". You don't have to commit to hard boundaries and you can 'repartition' (aka grow or shrink (if the FS permits) on a live system.
While I recognize the advantages of LVM, I never use it, simply because I have not memorized how it works, and in the case of problems I would be dead in the water. I prefer something that I can rescue without help, something that I do understand. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-02-20 1:23 p.m., Carlos E. R. wrote:
While I recognize the advantages of LVM, I never use it, simply because I have not memorized how it works, and in the case of problems I would be dead in the water. I prefer something that I can rescue without help, something that I do understand.
Well DUH! I've nee 'using' it for a long time. But I rarely have to initialize a new drive, and many months go by when i have no need to work on a LE. So I too have not memorized any of it. *EVERY* time I do anything with it I bring up the man pages, well actually I 'apropos lvm' then 'apropos create' so as to find the manual pages to read. As for 'rescue; well I almost always work from a live CD/USB, most often Knoppix 'cos it is the most robust, the most general. And yes it understands openSUSE LVM and file systems. (It also works on laptops in stores when no other Linux will boot; which says something about laptops ...) At this point I pull out a notebook I have on how to get at other FS with some pages from the Arch Wiki stapled in on how to do a series of 'foreign repairs and mounts' and then finally a CHROOT. It's over 2 years since I hast had to do that -- openSUSE 42.3 seems remarkably stable and the 4.20 series kernel delightful. So much so I'm really reluctant to 'upgrade' to "15". The "help" is just tools. The problems I have had, well, you can go back and look in the archives, have *ALL* been with file systems. Many of them are dumb problems like the tools for XFS not being up to date 'automatically', so I couldn't repair. Given the quality of the architecture and coding, I really wish ReiserFS was multi-threaded since it has been no problem at all apart for the drop in system performance when I have too many FS using it. I really wish someone would sponsor Reiser4. But LVM has been problem free. There seems to be quality code here. The one 'problem' I had was not really a LVM problem it was a systemd problem, the start-up of a management daemon, lvmetad. And that was well documented on the web. And the learning curve to use LVM is not steep. There is a wonderful paper by Michael Hasenstein <mha@suse.com> dating from 2001 on how to set-up and use LVM He points out that SUSE has included the LVM since Linux 6.3. ftp://biologs.bf.lu.lv/pub/OS/datori/Compaq/Proliant350/linux/lvm_whitepaper.pdf See also https://www.researchgate.net/publication/265867267_Implementation_of_Hardwar... https://landley.net/kdocs/ols/2002/ols2002-pages-117-129.pdf and annoyingly: https://patents.google.com/patent/US7627776 -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2019-02-20 at 14:23 -0500, Anton Aylward wrote:
On 2019-02-20 1:23 p.m., Carlos E. R. wrote:
While I recognize the advantages of LVM, I never use it, simply because I have not memorized how it works, and in the case of problems I would be dead in the water. I prefer something that I can rescue without help, something that I do understand.
Well DUH! I've nee 'using' it for a long time. But I rarely have to initialize a new drive, and many months go by when i have no need to work on a LE. So I too have not memorized any of it. *EVERY* time I do anything with it I bring up the man pages, well actually I 'apropos lvm' then 'apropos create' so as to find the manual pages to read.
But I don't need any of that with traditional partitioning, btrfs excluded. I insist that I fully appreciate the advantages of LVM, but it simply is not worth it for me. For similar reasons I also reject btrfs. :-) - -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXG6Enxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV8toAn1AI2a1X6UIiuXTE9p0s +PyW5xNjAJsEk6+Le2XxuFh3xzmyJRQXLqeB1Q== =bn4B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-02-21 5:59 a.m., Carlos E. R. wrote:
On Wednesday, 2019-02-20 at 14:23 -0500, Anton Aylward wrote:
On 2019-02-20 1:23 p.m., Carlos E. R. wrote:
While I recognize the advantages of LVM, I never use it, simply because I have not memorized how it works, and in the case of problems I would be dead in the water. I prefer something that I can rescue without help, something that I do understand.
Well DUH! I've nee 'using' it for a long time. But I rarely have to initialize a new drive, and many months go by when i have no need to work on a LE. So I too have not memorized any of it. *EVERY* time I do anything with it I bring up the man pages, well actually I 'apropos lvm' then 'apropos create' so as to find the manual pages to read.
But I don't need any of that with traditional partitioning, btrfs excluded.
I insist that I fully appreciate the advantages of LVM, but it simply is not worth it for me. For similar reasons I also reject btrfs. :-)
There is one over-riding reason I favour LVM over fdisk. Deferred Design. The issue of repartitioning, growth of file systems, come up here so often. We also get questions about migrating to a new drive or new partition. And now we have Jim's question about partitioning of a new drive. With LVM these all become trivial, non-issues, non-problems. With fdisk and rigid partitions you make decisions that are constraining, constricting and binding and it is a lot of work to change them; at the very least you have to shut down your machine. There are many business environments where that isn't feasible. But ultimately is it about not having to face those constraints, its about Deferred Design. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/02/2019 14.00, Anton Aylward wrote:
On 2019-02-21 5:59 a.m., Carlos E. R. wrote:
There is one over-riding reason I favour LVM over fdisk.
Deferred Design.
The issue of repartitioning, growth of file systems, come up here so often. We also get questions about migrating to a new drive or new partition. And now we have Jim's question about partitioning of a new drive. With LVM these all become trivial, non-issues, non-problems.
It just converts into another set of problems :-)
With fdisk and rigid partitions you make decisions that are constraining, constricting and binding and it is a lot of work to change them; at the very least you have to shut down your machine. There are many business environments where that isn't feasible.
Ah, but we are not talking business :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-02-21 8:49 a.m., Carlos E. R. wrote:
On 21/02/2019 14.00, Anton Aylward wrote:
On 2019-02-21 5:59 a.m., Carlos E. R. wrote:
There is one over-riding reason I favour LVM over fdisk.
Deferred Design.
The issue of repartitioning, growth of file systems, come up here so often. We also get questions about migrating to a new drive or new partition. And now we have Jim's question about partitioning of a new drive. With LVM these all become trivial, non-issues, non-problems.
It just converts into another set of problems :-)
Perhaps; but I've not found that to be the case. Perhaps that should be expressed a 'a smaller set of more easily addressed problems" then.
With fdisk and rigid partitions you make decisions that are constraining, constricting and binding and it is a lot of work to change them; at the very least you have to shut down your machine. There are many business environments where that isn't feasible.
Ah, but we are not talking business :-)
Oh,that canard come round again. Saying that we 'home users' are 'not professionals'. so we don't need professional quality software. I argued against that in the 1970s at various computer clubs. Professional grade, business grade, software is a matter of attitude and attention. It is equally applicable to the least of us. And many of us run small businesses as well as being involved with larger ones.Many of us run our own web sites and don't want unnecessary down-time just to manage file system size or introduce a new drive for 'more space'. And many of us don't know now what the requirements, the details will be, a week, a month from now, Which is why Deferred Design is so important. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 20 Feb 2019 19:23:23 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
While I recognize the advantages of LVM, I never use it, simply because I have not memorized how it works,
Well, that's what documentation is for. Search for 'lvm', or 'lvm yast' and take your pick.
and in the case of problems I would be dead in the water.
And that's what a second machine is for, or sometimes just another installation on the same machine, or a system-on-a-stick.
I prefer something that I can rescue without help, something that I do understand.
You can do the first part, using documentation and alternative systems. The second part follows naturally with repetition. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/02/2019 21.02, Dave Howorth wrote:
On Wed, 20 Feb 2019 19:23:23 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
While I recognize the advantages of LVM, I never use it, simply because I have not memorized how it works,
Well, that's what documentation is for. Search for 'lvm', or 'lvm yast' and take your pick.
I did read it, many years ago, and decided against it, unless on enterprise setup, thus paid to do it.
and in the case of problems I would be dead in the water.
And that's what a second machine is for, or sometimes just another installation on the same machine, or a system-on-a-stick.
I have all that, and still decided against :-)
I prefer something that I can rescue without help, something that I do understand.
You can do the first part, using documentation and alternative systems. The second part follows naturally with repetition.
I do not want disaster recovery repetition, thanks :-p -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-02-20 4:38 p.m., Carlos E. R. wrote:
I do not want disaster recovery repetition, thanks :-P
None of us do. But there is a reason we have fire engines, lifeboats ... Oh, and backups. You do make backups, don't you? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/02/2019 14.26, Anton Aylward wrote:
On 2019-02-20 4:38 p.m., Carlos E. R. wrote:
I do not want disaster recovery repetition, thanks :-P
None of us do. But there is a reason we have fire engines, lifeboats ... Oh, and backups. You do make backups, don't you?
Sure. And I also do not install LVM. :-p I do not know how to repair it, and I do not want to make the effort to learn how. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-02-21 8:44 a.m., Carlos E. R. wrote:
On 21/02/2019 14.26, Anton Aylward wrote:
On 2019-02-20 4:38 p.m., Carlos E. R. wrote:
I do not want disaster recovery repetition, thanks :-P
None of us do. But there is a reason we have fire engines, lifeboats ... Oh, and backups. You do make backups, don't you?
Sure. And I also do not install LVM. :-p
I do not know how to repair it, and I do not want to make the effort to learn how.
LVM came out with openSUSE 6. I've had to repair: - the kernel - XFS - BtrFS - Ext2,3,4 - the FUSE engine - systemd - SSHd I've had to clean up mistakes with fdisk family and different types of drives. I've had pains with partition sizing before I began using LVM and growable/shrinkable file systems like ReiserFS. I've NEVER had to repair: - LVM - ReiserFS -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/02/2019 14.54, Anton Aylward wrote:
On 2019-02-21 8:44 a.m., Carlos E. R. wrote:
I've had pains with partition sizing before I began using LVM and growable/shrinkable file systems like ReiserFS.
I've NEVER had to repair: - LVM
But I have seen people having to, not knowing how, asking here or elsewhere, and having to wait days, till finally been able to repair, or maybe not. I do not want that extra hassle on my home. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Le 21/02/2019 à 14:54, Anton Aylward a écrit :
I've NEVER had to repair: - LVM - ReiserFS
I had to repair one computer (not mine) installed with lvm and mounting root what pretty hard for me notice I'm also at pain with the change from ifconfig... jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-02-20 3:02 p.m., Dave Howorth wrote:
On Wed, 20 Feb 2019 19:23:23 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
While I recognize the advantages of LVM, I never use it, simply because I have not memorized how it works,
Well, that's what documentation is for. Search for 'lvm', or 'lvm yast' and take your pick.
I am continually amazed at home many Linux practitioners, even longer term ones, are unaware of 'apropos.
and in the case of problems I would be dead in the water.
And that's what a second machine is for, or sometimes just another installation on the same machine, or a system-on-a-stick.
.. or a tablet or a phone ... (or do you only use your phone for 'social' services?) Heck, those portable devices run on batteries so work even when the PC doesn't!
I prefer something that I can rescue without help, something that I do understand.
You can do the first part, using documentation and alternative systems. The second part follows naturally with repetition.
Regular readers will recall my obsession with documentation & records and such. What is apropos here is that even when I think I know what I'm doing I check the documentation. Sometimes you have to get things done before the sun rises (such as the pilot light on the furnace going out as it has this morning) when you don't have enough coffee in your bloodstream to be sure that memory suffices. You might recall that despite their intense and comprehensive training the US astronauts were supplied with small, laminated 'flip books' of various procedures, check lists. Maybe NASA thought microgravity would affect their memory, but experience on Earth has shown that taking the time to get critical procedures right, having those check-lists to help and that second set of eyes to verify does make a difference in the quality and reliability of the results. It would be arrogant of me to assume that I don't need a proof reader, be it for my emails, my reports or my letters home, even if I do write them after sun-up and after imbibing a few jars (read 'Venti'-sized) of coffee. (I dare not use Google speech-to-text with my accent at any time of the day!) But don't let that stop you; I'm sure it impresses the kiddies. (My coffee maker is electric.) (Time for another cup, then off to try and restart the furnace.) -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/21/2019 05:24 AM, Anton Aylward wrote:
But don't let that stop you; I'm sure it impresses the kiddies.
(My coffee maker is electric.) (Time for another cup, then off to try and restart the furnace.)
Did the fire go out and now you have to shovel some coal? :-) BTW, I remember residential coal furnaces as a kid. The coal truck would deliver a ton or two of coal down a chute, through an open basement window, to the coal bin. You'd then have to start a fire in the boiler and keep it going with subsequent shovel fulls of coal. This was in New Jersey, about 30-miles west of New York City. It is really amazing how much better life has gotten over such a short span of time. I think I already shared this clip of the opening of the Nine-Foot Channel on the Ohio River in 1929. https://www.youtube.com/watch?v=uBPtBlFI2mA It's amazing to me that steam sternwheelers where still so much in use! And all the coal smoke! And they were proud of it! Note the brakeman standing on top of their moving steam train close to the end of the clip. You never see that happening now, way too dangerous! The steam whistles were also impressive. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/21/2019 09:39 AM, Lew Wolfgang wrote:
(My coffee maker is electric.) (Time for another cup, then off to try and restart the furnace.)
Did the fire go out and now you have to shovel some coal? :-)
Well, shovel something. ;-)
BTW, I remember residential coal furnaces as a kid. The coal truck would deliver a ton or two of coal down a chute, through an open basement window, to the coal bin. You'd then have to start a fire in the boiler and keep it going with subsequent shovel fulls of coal. This was in New Jersey, about 30-miles west of New York City.
I also remember coal. While our house had an oil furnace, there were still some around where they burned coal but then converted to oil and later gas. The school I went to also burned coal, before switching to oil. These days, everyone burns natural gas. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 21 februari 2019 15:49:29 CET schreef James Knott:
On 02/21/2019 09:39 AM, Lew Wolfgang wrote:
(My coffee maker is electric.) (Time for another cup, then off to try and restart the furnace.)
Did the fire go out and now you have to shovel some coal? :-)
Well, shovel something. ;-)
BTW, I remember residential coal furnaces as a kid. The coal truck would deliver a ton or two of coal down a chute, through an open basement window, to the coal bin. You'd then have to start a fire in the boiler and keep it going with subsequent shovel fulls of coal. This was in New Jersey, about 30-miles west of New York City.
I also remember coal. While our house had an oil furnace, there were still some around where they burned coal but then converted to oil and later gas. The school I went to also burned coal, before switching to oil. These days, everyone burns natural gas. No, these days houses are built with no natural gas, oil etc. over here. This due to earthquakes generated by pumping up billions of m3 of natural gas. The move to solar and wind energy is actually taking place. And re. natural gas, the NL were the Russia of the 1960s. And until the 1980s no one worried about the earthquakes. Then some people warned, but hey, our national wealth was depending on it, so let's ignore it until it becomes a real problem. Which happened over the last decade.
And yes, I remember coal. In the 1960s, wednesday was the day coal ( and natural gas in bottles ) was delivered, by horse and carriage....... :). -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Knurpht-openSUSE <knurpht@opensuse.org> [02-21-19 10:52]: [...]
And yes, I remember coal. In the 1960s, wednesday was the day coal ( and natural gas in bottles ) was delivered, by horse and carriage....... :).
yes, we had it in the '40s but was delivered by a truck. few horses on the roads in town then, even the small town of < 1000 where I lived. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/21/2019 08:07 AM, Patrick Shanahan wrote:
* Knurpht-openSUSE <knurpht@opensuse.org> [02-21-19 10:52]: [...]
And yes, I remember coal. In the 1960s, wednesday was the day coal ( and natural gas in bottles ) was delivered, by horse and carriage....... :). yes, we had it in the '40s but was delivered by a truck. few horses on the roads in town then, even the small town of < 1000 where I lived.
I remember only one horse-drawn wagon as a kid. This was late '40s, very early '50s. It was a "rag picker" IIRC. Funny what you remember as a small kid. My first memory was of me sticking a metal hair-pin into an electrical outlet. That set the tone for the rest of my life! Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Lew Wolfgang <wolfgang@sweet-haven.com> [02-21-19 12:33]:
On 02/21/2019 08:07 AM, Patrick Shanahan wrote:
* Knurpht-openSUSE <knurpht@opensuse.org> [02-21-19 10:52]: [...]
And yes, I remember coal. In the 1960s, wednesday was the day coal ( and natural gas in bottles ) was delivered, by horse and carriage....... :). yes, we had it in the '40s but was delivered by a truck. few horses on the roads in town then, even the small town of < 1000 where I lived.
I remember only one horse-drawn wagon as a kid. This was late '40s, very early '50s. It was a "rag picker" IIRC. Funny what you remember as a small kid. My first memory was of me sticking a metal hair-pin into an electrical outlet. That set the tone for the rest of my life!
I remember jumping off the porch which was too high and putting my finger into a fan which had cloth blades. now the porch is again probably too high :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/2/19 6:07 am, Patrick Shanahan wrote:
* Lew Wolfgang <wolfgang@sweet-haven.com> [02-21-19 12:33]:
On 02/21/2019 08:07 AM, Patrick Shanahan wrote:
* Knurpht-openSUSE <knurpht@opensuse.org> [02-21-19 10:52]: [...]
And yes, I remember coal. In the 1960s, wednesday was the day coal ( and natural gas in bottles ) was delivered, by horse and carriage....... :). yes, we had it in the '40s but was delivered by a truck. few horses on the roads in town then, even the small town of < 1000 where I lived. I remember only one horse-drawn wagon as a kid.� This was late '40s, very early '50s.� It was a "rag picker" IIRC.� Funny what you remember as a small kid.� My first memory was of me sticking a metal hair-pin into an electrical outlet.� That set the tone for the rest of my life! I remember jumping off the porch which was too high and putting my finger into a fan which had cloth blades.
now the porch is again probably too high :)
Patrick, old sausage, what does coal have anything to do with the partitioning question Jim asked in this list oriented towards solving technical matters, hmmm? :-) Desist, I say! :-) BC -- 'When I use a word', Humpty Dumpty said, in a rather scornful tone, 'it means just what I choose it to mean.' Lewis Carroll, Through the Looking-Glass -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/19/2019 08:10 PM, Jim Flanagan wrote:
Hi guys,
I know this has been asked many times, and probably by me more than once, but here goes again. I finally got an SSD which I'd like to install on my Linux box. Yea! Starting off with a new drive I have the luxury to start fresh, i.e. place grub where I want. But, I liked to maintain my existing installs as bootable at least for a while while I get the new install set up properly. But new install on a new drive gives me that chance to re-think my past partitioning setup and bring it up to current thinking.
<snip>
My new SSD is a 120GB Kingston. I don't think I could do the 2 separate partition installs on this as my current partition is 100GB with about 50GB free. I don't want to limit my working space too much. The 120GB drive would give me about 50 or 55GB space for each of the two and I feel that's too limiting. I do plan on keeping teh current sda for large files and other storage to save space on the SSD.
Jim, In the past, I've done it several ways. All the way from separate: for servers /boot / /home /srv (for website backup) /var (for mysql and groupware backups) But today I basically do / /home and in some cases just /. With a 120G SSD, I would take the / route and I would use ext4 NOT btrfs. I'd download the network install image and burn it to a flash drive or CD and just install as normal. You will have to argue with the partitioner to let you change from btrfs to ext4, but after that it is up to you whether you use a traditional 'root' account (I always do) and the remainder of the install is the normal YAST install. If this is your first SSD, you will be pleased. With 42.3, I go from power-button ON to full kdm3/KDE3 desktop in 11.1 seconds (done). Logging in and bringing up the full desktop takes a hair over 1 second. Responsiveness is instantaneous. Even loading LibreOffice or Gimp is less than 2 seconds. I did go with a traditional /, /home, swap on my 42.3 laptop, and I have no complaints, e.g. $ cat /proc/partitions major minor #blocks name 8 0 244198584 sda <win10 SSD> 8 1 102400 sda1 8 2 242337644 sda2 8 3 902144 sda3 8 4 851948 sda4 8 16 488386584 sdb <Linux SSD> 8 17 2103296 sdb1 <-- swap 8 18 41946112 sdb2 <-- root 8 19 444336128 sdb3 <-- home 11 0 1048575 sr0 $ grep sdb /proc/mounts /dev/sdb2 / ext4 rw,noatime,data=ordered 0 0 /dev/sdb3 /home ext4 rw,noatime,data=ordered 0 0 I'd load 15. I have both 42.3 and 15.0 and have had no problems with either. Just very enjoyable. Don't know what your favorite desktop is, but I have KDE3 on both and it is in the best shape it has ever been in. Good luck with your install. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2/20/19 10:48 AM, David C. Rankin wrote:
On 02/19/2019 08:10 PM, Jim Flanagan wrote:
Hi guys,
I know this has been asked many times, and probably by me more than once, but here goes again. I finally got an SSD which I'd like to install on my Linux box. Yea! Starting off with a new drive I have the luxury to start fresh, i.e. place grub where I want. But, I liked to maintain my existing installs as bootable at least for a while while I get the new install set up properly. But new install on a new drive gives me that chance to re-think my past partitioning setup and bring it up to current thinking.
<snip>
My new SSD is a 120GB Kingston. I don't think I could do the 2 separate partition installs on this as my current partition is 100GB with about 50GB free. I don't want to limit my working space too much. The 120GB drive would give me about 50 or 55GB space for each of the two and I feel that's too limiting. I do plan on keeping teh current sda for large files and other storage to save space on the SSD.
Jim,
In the past, I've done it several ways. All the way from separate:
for servers
/boot / /home /srv (for website backup) /var (for mysql and groupware backups)
But today I basically do
/ /home
and in some cases just /.
David, Thanks for the help. Install went well. This thing if FAST!! Can't beleive I've waited all this time to get an SSD but glad I did. Grub won't boot to the older 42.3 install, but I'll start another thread if I can't figure it out. See my note to Carlos, but I took the default / as BtrFS and /home as XFS. You may find this interesting, but when I did the 42.3 install, I also went with BtrFS, but all on /. But, I deleted all the recommended sub-volumes at that time. I didn't understand why they were needed then on this file system, but now I do. Good documentation online, thanks OpenSuSE Team!! Much appreciated. Jim F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/25/2019 04:48 PM, Jim Flanagan wrote:
David,
Thanks for the help. Install went well. This thing if FAST!! Can't beleive I've waited all this time to get an SSD but glad I did.
I had the same reaction. To go from pushing the power button to a full KDE3 desktop in 11 seconds almost 4 times faster than the spinning SATA II driver would do. Blew me away. Grub won't boot to the
older 42.3 install, but I'll start another thread if I can't figure it out.
This is just a config issue, no limitation on mixing SSD and platters from a GRUB standpoint. You just need to add an entry to boot your 42.3 install to the new GRUB install on your current SSD.
See my note to Carlos, but I took the default / as BtrFS and /home as XFS. You may find this interesting, but when I did the 42.3 install, I also went with BtrFS, but all on /. But, I deleted all the recommended sub-volumes at that time. I didn't understand why they were needed then on this file system, but now I do. Good documentation online, thanks OpenSuSE Team!!
That I do find interesting. I'll also be very interested 6 months from now to hear if you have had any Oopsies... with snapshots or other common issues robbing you of your drive space. Good data points there are just as useful as bad ones. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Jim Flanagan composed on 2019-02-19 21:10 (UTC-0500):
My new SSD is a 120GB Kingston. I don't think I could do the 2 separate partition installs on this as my current partition is 100GB with about 50GB free. I don't want to limit my working space too much. The 120GB drive would give me about 50 or 55GB space for each of the two and I feel that's too limiting. I do plan on keeping teh current sda for large files and other storage to save space on the SSD.
I bought a 120G SSD last June for $30 USD: # parted -l Model: ATA MKNSSDSR120GB (scsi) Disk /dev/sda: 120GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 337MB 336MB fat16 M12P01 EFI System (ESP) boot, esp 2 337MB 2174MB 1837MB linux-swap(v1) M12P02 Linux Swap swap 3 2174MB 2593MB 419MB ext2 M12P03 Linux reservation 4 2593MB 6787MB 4194MB ext4 M12P04 Linux /usr/local 5 6787MB 13.5GB 6711MB ext4 M12P05 Linux /home 6 13.5GB 26.7GB 13.2GB ext4 M12P06 Linux /secret 7 26.7GB 35.1GB 8389MB ext4 M12P07 openSUSE Tumbleweed 8 35.1GB 43.5GB 8389MB ext4 M12P08 openSUSE 15.0 9 43.5GB 51.9GB 8389MB ext4 M12P09 openSUSE 15.1 10 51.9GB 60.3GB 8389MB ext4 M12P10 Debian 10 Buster 11 60.3GB 68.7GB 8389MB ext4 M12P11 Debian 10 Fat Buster 12 68.7GB 77.0GB 8389MB ext4 M12P12 Ubuntu 18.04 Bionic 13 77.0GB 85.4GB 8389MB ext4 M12P13 LinuxMint 19 XFCE 14 85.4GB 93.8GB 8389MB ext4 M12P14 Buster mini mini 15 93.8GB 102GB 8389MB ext4 M12P15 Buster standard 16 102GB 111GB 8389MB ext4 M12P16 Linux Data todo Given the amount of space you will have available for user data on the other two drives, 120 should be plenty of space for two system installation partitions that each include /home, plus a swap partition, particularly if you stick with EXT4 instead of BTRFS, for which recommend filesystem size is double that of EXT4. The limiting you sense is largely because of BTRFS snapshotting. Even if you stick with BTRFS, you should have more than 133% of recommended minimum system partition space for each. If our SSD purchase experience is any guide, you should expect to be able to buy a 240G SSD before 15.0 is out of support for about the same price you just paid for 120G. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2/21/19 8:16 AM, Felix Miata wrote:
I bought a 120G SSD last June for $30 USD: # parted -l Model: ATA MKNSSDSR120GB (scsi) Disk /dev/sda: 120GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags:
Number Start End Size File system Name Flags 1 1049kB 337MB 336MB fat16 M12P01 EFI System (ESP) boot, esp 2 337MB 2174MB 1837MB linux-swap(v1) M12P02 Linux Swap swap 3 2174MB 2593MB 419MB ext2 M12P03 Linux reservation 4 2593MB 6787MB 4194MB ext4 M12P04 Linux /usr/local 5 6787MB 13.5GB 6711MB ext4 M12P05 Linux /home 6 13.5GB 26.7GB 13.2GB ext4 M12P06 Linux /secret 7 26.7GB 35.1GB 8389MB ext4 M12P07 openSUSE Tumbleweed 8 35.1GB 43.5GB 8389MB ext4 M12P08 openSUSE 15.0 9 43.5GB 51.9GB 8389MB ext4 M12P09 openSUSE 15.1 10 51.9GB 60.3GB 8389MB ext4 M12P10 Debian 10 Buster 11 60.3GB 68.7GB 8389MB ext4 M12P11 Debian 10 Fat Buster 12 68.7GB 77.0GB 8389MB ext4 M12P12 Ubuntu 18.04 Bionic 13 77.0GB 85.4GB 8389MB ext4 M12P13 LinuxMint 19 XFCE 14 85.4GB 93.8GB 8389MB ext4 M12P14 Buster mini mini 15 93.8GB 102GB 8389MB ext4 M12P15 Buster standard 16 102GB 111GB 8389MB ext4 M12P16 Linux Data todo
Nice layout! ;-) One addition: if one needs the 'texlive-*' packages (and wanted them to have on '/'), then I'd suggest to increase the size for '/' to e.g. 14-16G. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/21/2019 01:16 AM, Felix Miata wrote:
I bought a 120G SSD last June for $30 USD: # parted -l Model: ATA MKNSSDSR120GB (scsi) Disk /dev/sda: 120GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags:
Number Start End Size File system Name Flags 1 1049kB 337MB 336MB fat16 M12P01 EFI System (ESP) boot, esp 2 337MB 2174MB 1837MB linux-swap(v1) M12P02 Linux Swap swap 3 2174MB 2593MB 419MB ext2 M12P03 Linux reservation 4 2593MB 6787MB 4194MB ext4 M12P04 Linux /usr/local <snip a bizallion more partitions>
I always knew you were working one brick shy of a full load ;-) That's the most partitions I've ever seen someone shoehorn onto a 128G drive :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin composed on 2019-02-21 17:20 (UTC-0600):
Felix Miata wrote:
Number Start End Size File system Name Flags 1 1049kB 337MB 336MB fat16 M12P01 EFI System (ESP) boot, esp ... 16 102GB 111GB 8389MB ext4 M12P16 Linux Data todo
I always knew you were working one brick shy of a full load ;-)
That's the most partitions I've ever seen someone shoehorn onto a 128G drive :)
16 partitions in 120G (7.5G per partition) is below average here. Others running Leap and/or TW (among others) include: t2240 80G ends w/ sda29 2.7G avg k8mmv 120G ends w/ sda28 4.4G avg m7ncd 160G ends w/ sda48 3.4G avg ei965 160G ends w/ sda58 3.6G avg :-D -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (14)
-
Anton Aylward -
Basil Chupin -
Bernhard Voelker -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Felix Miata -
James Knott -
jdd＠dodin.org -
Jim Flanagan -
Knurpht-openSUSE -
Lew Wolfgang -
Patrick Shanahan -
Roger Price