From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Michael's ArchLinux Installation
Date: Mon, 26 Apr 2010 21:36:17 +0800 [thread overview]
Message-ID: <D9F1D99F4F41479D97A9BF9BD5948AAD@bouncy> (raw)
In-Reply-To: <4BD58A86.9050508@aim.com>
Ok lvm does allow more flexibility however there are some limits.
You can use just ramsize for swap, so 2gb would be enough and this would let
you suspend to disk.
You can resize partitions with lvm however you need to resize the underlying
filesystem first. You can't resize a mounted filesystem so resizing the root
file system won't happen unless you boot from a live cd.
Usually what happens is you have a /boot partition and then the rest of the
system loads off logical volumes. To do this however you need an initial
ramdisk and lvm built into that initial ramdisk image. This is something i'm
sure arch linux has.
I often actually set up /boot with say 100 megabytes, then a small root fs
then the rest of the stuff on logical volumes.
To change the size of partitions you need to reduce the size of the file
system then reduce the number of logical extents in the file system. not
sure if there are tools to do this easily.
I think you can grow reiserfs when it is mounted but shrinking it requires
an unmount.
xfs can only grow.
ext4 I believe needs to be unnmounted for resizing.
If diskspace is tight then perhaps doing without lvm would save you
complexity.
the smallest disk I have in a server is 60 gig so space is not an issue
here.
I don't usually use lvm on the virtual machines which are 2 gig in size,
they don't need the complexity.
As to the comment on swap, I don't see a lot of stuff swapped out but if
there is no swap then swapping is not an option.
Yes the system can swap to lvm although note that you need support in the
initrd for the s2disk technology either the kernel stuff or tuxonice.
Regards, Kerry.
----- Original Message -----
From: "Michael Whapples" <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, April 26, 2010 8:43 PM
Subject: Re: Michael's ArchLinux Installation
> Thanks for the information. I did sort of know about the suspend to disk
> advantage.
>
> I do have a question. As my reason for using swap files for swap space is
> to do with having 2GB of RAM and so using the RAM times two rule for swap
> means 4GB which is more than I think my laptop's HD wants to take
> permanently (I mean it would restrict the other partitions more than I
> would want to go). Now I have heard people mention about LVM allowing more
> dynamic allocation of disk space, how possible are the following and how
> safe are they:
>
> * To expand and shrink volumes with data on (eg. an ext4 partition holding
> the main system)?
> * Suspend to disk, does it work if swap is a volume in LVM?
> * Is there any issues with using swap in a volume?
> * What is the options for installing grub when using LVM? Remember my
> preference has been to install it to the partition boot sector.
>
> Thanks for any answers.
>
> Michael Whapples
> On 01/-10/-28163 08:59 PM, Jason White wrote:
>> "Kerry Hoath"<kerry@gotss.net> writes:
>>
>>
>>> There are advantages to having a swap partition.
>>> Firstly, accessing a partition directly for virtual memory bypasses
>>> file system overhead. You can just read/write pages to absolute
>>> sectors on the partition.
>>>
>> True, although I have read claims that under modern Linux kernels, it is
>> no longer the case that swap partitions give higher performance than
>> swap files. Regrettably I can't remember the details, but I assume that
>> since space for the swap files is pre-allocated, the kernel now keeps
>> track of where the sectors are on the device so that it doesn't have to
>> invoke the file system when writing to the swap space.
>>
>> The other advantages mentioned are uncontroversially correct, though, as
>> far as I know.
>>
>>
>>
>>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
JP Jamous
` Tyler Littlefield
` Glenn Ervin
` Tyler Littlefield
` Gregory Nowak
` trev.saunders
` Michael Whapples
` Farhan
` Gregory Nowak
` JP Jamous
` Michael Whapples
` Chris Brannon
` JP Jamous
` Glenn Ervin
` trev.saunders
` Michael Whapples
` Kerry Hoath
` Jason White
` Michael Whapples
` trev.saunders
` Kerry Hoath [this message]
` Michael Whapples
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D9F1D99F4F41479D97A9BF9BD5948AAD@bouncy \
--to=kerry@gotss.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).