From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2EAF8138CC5 for ; Mon, 4 May 2015 07:39:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C73A0E08BB; Mon, 4 May 2015 07:39:13 +0000 (UTC) Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com [209.85.220.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 84348E0848 for ; Mon, 4 May 2015 07:39:12 +0000 (UTC) Received: by qku63 with SMTP id 63so80003306qku.3 for ; Mon, 04 May 2015 00:39:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=UDtwksjWFIBKT/9qNt0+3NwoTKjdezmedN4sqG1jXpI=; b=sBQjbJUbS0V9Rjy8cM1W5ccZTf/Bl6h1K6h/9Ib7qA7eAupQ9txeki0GfCmqIy0cCi TqqYrvCCn9t66utXOBaNYyoJafh8iYeZbNEmTNKossUREx02PECR+ETVj7pYme3jkD02 CFcXFZWgreOo1iDHno5MeZ8FwI1GxdaCL8kRoxlg2eZ6VaC0U6Oq5URt88d+T5ByT4Lm lbZGpquUVmZbnvZ5hD5Dz/goHmMeeU2MQiU3Mdmehk9fa625VI6f7pprn2AVMkFF2Sah BFouhjWD1pcRjy91yuhqCytMAGmJXTHId7B3eaAxfJGdaVJagcLueQFJqMn2DG5qWsJz qhhQ== X-Received: by 10.55.50.201 with SMTP id y192mr42251170qky.10.1430725151907; Mon, 04 May 2015 00:39:11 -0700 (PDT) Received: from [192.168.2.5] (adsl-98-95-106-170.jan.bellsouth.net. [98.95.106.170]) by mx.google.com with ESMTPSA id x142sm9231457qkx.28.2015.05.04.00.39.10 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 May 2015 00:39:11 -0700 (PDT) Message-ID: <5547221E.4020809@gmail.com> Date: Mon, 04 May 2015 02:39:10 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Hard drive storage questions References: <553F474E.4040101@gmail.com> <553FA0DD.1090101@gmail.com> <20150428162448.160e1683@digimed.co.uk> <55407695.7000808@gmail.com> <20150429085217.38864030@hactar.digimed.co.uk> In-Reply-To: <20150429085217.38864030@hactar.digimed.co.uk> Content-Type: multipart/alternative; boundary="------------060609030700050800050905" X-Archives-Salt: e952ec53-3619-4936-bd36-b871e2a15bcd X-Archives-Hash: 169fbb696a5842fa5b7e9c6059a42d9d This is a multi-part message in MIME format. --------------060609030700050800050905 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Neil Bothwick wrote: > On Wed, 29 Apr 2015 08:13:41 +0200, Alan McKinnon wrote: > >>> An alternative is to create a new volume group on the new disk and >>> mounts PVs at various points in your home directory. That way you get= >>> the extra space and much of the flexibility without the risk of a >>> failure on a single drive taking out data on both. However, if you >>> are concerned about data loss, you should be using RAID at a minimum,= >>> preferably with an error detecting filesystem.=20 >> >> I've used that scheme myself in the past. You do get the increased spa= ce >> but you don't get much in the way of flexibility. And it get COMPLICAT= ED >> really quickly. > > It certainly can, but for a simple two drive home system it shouldn't g= et > out of hand. However, it does avoid the "one disk errors kills two > disks' data" problem. Yea, right now, I'm only using two drives. One for the OS and one for /home. I have a third drive but it isn't in use. I'm thinking about moving everything but the videos to that drive, 750GB, and leave just the videos on the large 3TB drive. It'll free up a *little* space too. > > >> To get around the situation of one drive almost full and the other >> having lots of space, folks often use symlinked directories, which you= >> forget about and no-one else can figure out what you did... > > I wasn't suggesting symlinks, just LVs mounted at appropriate points. I= t > rather depends on the spread of Dale's data. If he just needs extra spa= ce > for his videos, he could get a new drive and mount it at ~/videos. The bulk of the space is used by the videos. It's everything from TV shows to movies to youtube howtos. I'm using roughly 1.8TB on the drive and the videos take up roughly 1.7TB of that space. My camera pics only use 21GBs of space. Rest is basically a rounding error. :/ > >> It all smacks of the old saw: >> >> For any non-trivial problem, there is always at least one solution tha= t >> is simple, elegant, and wrong. > > :-) > > I consider what I suggested somewhat simple but far from elegant. Often= > though, it's a lot less work in the long run to go for the initially mo= re > complex solution. If Dale is worried about the likelihood of disk > failure, he really should be using RAID - either MDRAID under LVM or on= e > of the next-gen filesystems. > > I really do need to set up RAID at least for some stuff that I may not be able to get back. Some videos I have are no longer available. What I wish, I had a second puter in a outbuilding that I could copy to over ethernet or something. May help in the event of a house fire etc. Dale :-) :-) --------------060609030700050800050905 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Neil Bothwick wrote:
> On Wed, 29 Apr 2015 08:13:41 +0200, Alan McKinnon wrote:
>
>>> An alternative is to create a new volume group on the new disk and
>>> mounts PVs at various points in your home directory. That way you get
>>> the extra space and much of the flexibility without the risk of a
>>> failure on a single drive taking out data on both. However, if you
>>> are concerned about data loss, you should be using RAID at a minimum,
>>> preferably with an error detecting filesystem. 
>>
>> I've used that scheme myself in the past. You do get the increased space
>> but you don't get much in the way of flexibility. And it get COMPLICATED
>> really quickly.
>
> It certainly can, but for a simple two drive home system it shouldn't get
> out of hand. However, it does avoid the "one disk errors kills two
> disks' data" problem.

Yea, right now, I'm only using two drives.  One for the OS and one for /home.  I have a third drive but it isn't in use.  I'm thinking about moving everything but the videos to that drive, 750GB, and leave just the videos on the large 3TB drive.  It'll free up a *little* space too.


>
>
>> To get around the situation of one drive almost full and the other
>> having lots of space, folks often use symlinked directories, which you
>> forget about and no-one else can figure out what you did...
>
> I wasn't suggesting symlinks, just LVs mounted at appropriate points. It
> rather depends on the spread of Dale's data. If he just needs extra space
> for his videos, he could get a new drive and mount it at ~/videos.

The bulk of the space is used by the videos.  It's everything from TV shows to movies to youtube howtos.  I'm using roughly 1.8TB on the drive and the videos take up roughly 1.7TB of that space.  My camera pics only use 21GBs of space.  Rest is basically a rounding error.  :/

>
>> It all smacks of the old saw:
>>
>> For any non-trivial problem, there is always at least one solution that
>> is simple, elegant, and wrong.
>
> :-)
>
> I consider what I suggested somewhat simple but far from elegant. Often
> though, it's a lot less work in the long run to go for the initially more
> complex solution. If Dale is worried about the likelihood of disk
> failure, he really should be using RAID - either MDRAID under LVM or one
> of the next-gen filesystems.
>
>

I really do need to set up RAID at least for some stuff that I may not be able to get back.  Some videos I have are no longer available.   What I wish, I had a second puter in a outbuilding that I could copy to over ethernet or something.  May help in the event of a house fire etc.

Dale

:-)  :-)

--------------060609030700050800050905--