1 |
> -----Original Message----- |
2 |
> From: Dale <rdalek1967@×××××.com> |
3 |
> Sent: Monday, April 4, 2022 5:42 AM |
4 |
> To: gentoo-user@l.g.o |
5 |
> Subject: Re: [gentoo-user] LVM and moving things around |
6 |
> |
7 |
> Bill Kenworthy wrote: |
8 |
> > Rsync has a bwlimit argument which helps here. Note that rsync copies |
9 |
> > the whole file on what it considers local storage (which can be |
10 |
> > mounted network shares) ... this can cause a real slowdown. |
11 |
> > BillK |
12 |
> > |
13 |
> > |
14 |
> |
15 |
> I ended up just letting it do its thing. I didn't want to slow it down by much, just make my desktop able to respond better. I used nice and ionice to do this with emerge and it works great. I just thought I was missing some option for that command that google didn't help with. I went and helped my sis-n-law with some garden stuff. That helped. ;-) |
16 |
> |
17 |
> As it stands now, I've copied enough over to get a free 8TB drive. I set up LUKS, which includes LVM, on the drive and am copying some more files onto the newly encrypted drive. Once everything is transferred, I'll then see if I need the other drive added or not. I may not at the moment. Of course, once fiber internet gets here, that may change pretty soon. |
18 |
> |
19 |
> If someone is really knowledgeable about LVM and LUKS and how to set up a encrypted hard drive, not a whole install but just a data drive, a howto for this would be really nice. I had to use a LUKS howto and a LVM howto and sort of merge commands until I figured out how to get the two together. Even tho I got it working, I'm still not real clear on how one part of it works. I'm just not clear enough on it to write one myself. A Gentoo wiki would be nice. There's one for the two separately but not together. One posted anywhere google can find it would be great tho. |
20 |
> |
21 |
> Now to find something to do while rsync copies over some 6TBs of files. O_O |
22 |
> |
23 |
> Dale |
24 |
> |
25 |
> :-) :-) |
26 |
> |
27 |
A little late to the party, but the other setting to look at when you're doing this kind of thing is "sysctl vm.dirty_ratio".
|
28 |
Basically it's what percentage of the disk cache can be dirty before the system forces all IO operations to be synchronous.
|
29 |
|
30 |
Setting it higher lets the system keep more data up-in-the-air while you're shuffling lots of stuff around. Of course, it also risks losing more if the system crashes in the middle of it all, so use it judiciously.
|
31 |
|
32 |
Setting dirty_ratio dirty_background_ratio, and dirty_writeback_centisecs appropriately when doing things with large amounts of data can significantly improve system responsiveness and, with rotational drives, throughput.
|
33 |
|
34 |
LMP |