From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Testing a used hard drive to make SURE it is good.
Date: Tue, 16 Jun 2020 09:22:30 +0100 [thread overview]
Message-ID: <5EE88146.1080208@youngman.org.uk> (raw)
In-Reply-To: <bf5c2c64-58ea-16f8-d22c-f94e4feaf254@gmail.com>
On 16/06/20 08:34, Dale wrote:
> Right now, I'm backing up to a 8TB external drive, sadly it is a SMR
> drive but it works. As I go along, I'll be breaking down my backups.
> Example. I may have my Documents directory, which includes my camera
> pics, backed up to one drive. I may have videos backed up to another
> drive. Other directories may have to be on other drives. The biggest
> things I don't want to lose: Camera pics that could not be replaced
> except with a backup. Videos, some of which are no longer available.
> That requires a large drive. It currently is approaching 6TBs and I
> have several videos in other locations that are not included in that.
> Documents which would be hard to recreate. Since I have all my emails
> locally, I don't want to lose those either. Just a bit ago, I was
> searching for posts regarding smartctl. I got quite a few hits.
Streaming to an SMR should be fine. Doing a cp to a new directory, or
writing a .tar file, or stuff like that.
What is NOT fine is anything that is likely to result in a lot of
head-seeking as files and directories get modified ...
Remember that when backing up - so a btrfs with snapshots, or an lvm
snapshot with rsync in place, is most definitely not a good idea with SMR.
Cheers,
Wol
next prev parent reply other threads:[~2020-06-16 8:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 16:07 [gentoo-user] Testing a used hard drive to make SURE it is good Dale
2020-06-15 19:20 ` Spackman, Chris
2020-06-15 19:54 ` Mark Knecht
2020-06-15 20:00 ` Rich Freeman
2020-06-15 20:04 ` Mark Knecht
2020-06-16 7:34 ` Dale
2020-06-16 8:22 ` Wols Lists [this message]
2020-06-16 9:04 ` Dale
2020-06-16 11:02 ` Wols Lists
2020-06-16 11:26 ` Dale
2020-06-16 11:36 ` Michael
2020-06-16 12:25 ` Rich Freeman
2020-06-16 23:38 ` antlists
2020-06-17 9:47 ` Rich Freeman
2020-06-23 16:14 ` Sid Spry
2020-06-23 17:20 ` Rich Freeman
2020-06-23 18:44 ` Sid Spry
2020-06-16 13:14 ` Dale
2020-06-16 23:24 ` antlists
2020-06-17 4:47 ` Dale
2020-06-17 12:32 ` Wols Lists
2020-06-17 12:04 ` Rich Freeman
2020-06-16 8:29 ` Neil Bothwick
2020-06-16 8:52 ` Dale
2020-06-15 19:54 ` [gentoo-user] " Grant Edwards
2020-06-15 20:04 ` Grant Edwards
2020-06-15 23:03 ` [gentoo-user] " madscientistatlarge
2020-06-15 23:18 ` David Haller
2020-06-16 7:17 ` Dale
2020-06-16 7:32 ` William Kenworthy
2020-06-16 7:37 ` Dale
2020-06-17 15:27 ` David Haller
2020-06-18 8:07 ` Dr Rainer Woitok
2020-06-23 16:08 ` Sid Spry
2020-06-23 16:38 ` [gentoo-user] " Grant Edwards
2020-06-23 16:41 ` Sid Spry
2020-06-23 17:26 ` Dale
2020-06-23 18:32 ` Sid Spry
2020-06-23 19:37 ` Dale
2020-06-23 20:03 ` Rich Freeman
2020-06-24 4:26 ` Wols Lists
2020-06-18 9:14 ` [gentoo-user] " Dale
2020-06-22 1:52 ` Pengcheng Xu
2020-06-22 2:15 ` Dale
2020-06-22 19:10 ` David Haller
2020-06-22 20:29 ` Dale
2020-06-22 22:59 ` David Haller
2020-06-23 4:18 ` Dale
2020-06-17 6:02 ` Dale
2020-06-20 9:50 ` Dale
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=5EE88146.1080208@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.org \
/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