On 2020-08-20 14:58, Andy Smith wrote:
... dm-integrity can now be used with LUKS (with or
without encryption) to add checksums that force a read error when
they don't match. When there is redundancy (e.g. LVM or MD) a read
can then come from a good copy and the bad copy will be repaired.
So,
On Thu, Aug 20, 2020 at 01:34:58PM -0700, David Christensen wrote:
> On 2020-08-20 08:32, rhkra...@gmail.com wrote:
> >On Thursday, August 20, 2020 03:43:55 AM to...@tuxteam.de wrote:
> >>Contraty to the other (very valid) points, my backups are always on
> >>a LUKS drive, no partition table. Ratio
Hello,
On Thu, Aug 20, 2020 at 05:30:20PM -0400, Dan Ritter wrote:
> David Christensen wrote:
> > Some people have mentioned md RAID. tomas has mentioned LUKS. I believe
> > both of them add checksums to the contained contents. So, bit-rot within a
> > container should be caught by the contain
David Christensen wrote:
> On 2020-08-20 08:32, rhkra...@gmail.com wrote:
> I have been pondering bit-rot mitigation on non-checksumming filesystems.
>
>
> Some people have mentioned md RAID. tomas has mentioned LUKS. I believe
> both of them add checksums to the contained contents. So, bit-r
On 2020-08-20 08:32, rhkra...@gmail.com wrote:
On Thursday, August 20, 2020 03:43:55 AM to...@tuxteam.de wrote:
Contraty to the other (very valid) points, my backups are always on
a LUKS drive, no partition table. Rationale is, should I lose it, the
less visible information the better. Best if i
On Thursday, August 20, 2020 03:43:55 AM to...@tuxteam.de wrote:
> Contraty to the other (very valid) points, my backups are always on
> a LUKS drive, no partition table. Rationale is, should I lose it, the
> less visible information the better. Best if it looks like a broken
> USB stick. No partit
On Thu, 20 Aug 2020 09:43:55 +0200
wrote:
> On Wed, Aug 19, 2020 at 02:41:02PM -0700, David Christensen wrote:
> > On 2020-08-19 03:03, Urs Thuermann wrote:
> > >David Christensen writes:
> >
> > >>When using a drive as backup media, are there likely use-cases
> > >>that benefit from conf
On Wed, Aug 19, 2020 at 02:41:02PM -0700, David Christensen wrote:
> On 2020-08-19 03:03, Urs Thuermann wrote:
> >David Christensen writes:
>
> >>When using a drive as backup media, are there likely use-cases that
> >>benefit from configuring the drive with no partition, a single PV,
> >>single V
On 2020-08-19 03:03, Urs Thuermann wrote:
David Christensen writes:
When using a drive as backup media, are there likely use-cases that
benefit from configuring the drive with no partition, a single PV,
single VG, single LV, and single filesystem vs. configuring the drive
with a single partit
David Christensen writes:
> Thanks for the explanation. It seems that pvcreate(8) places an LVM
> disk label and an LVM metadata area onto disks or partitions when
> creating a PV; including a unique UUID:
>
> https://www.man7.org/linux/man-pages/man8/pvcreate.8.html
Yes, correct. You can see
On 2020-08-18 23:00, Urs Thuermann wrote:
David Christensen writes:
AIUI the OP was mounting an (external?) drive partition for use as a
destination for backups. Prior to upgrading to Testing, the root
partition was /dev/sda1 (no LVM?) and the backup partition was
/dev/sdb1 (no LVM?). After
Urs Thuermann writes:
> IMO the best solution is to use LVM. I use it since 2001 on most
> drives and I don't have partitions. And I prefer to use device names
> over using the *UUID or *LABEL prefixes. With LVM, device names are
> predictable /dev/mapper/- with symlinks
> /dev//.
Following u
David Christensen writes:
> AIUI the OP was mounting an (external?) drive partition for use as a
> destination for backups. Prior to upgrading to Testing, the root
> partition was /dev/sda1 (no LVM?) and the backup partition was
> /dev/sdb1 (no LVM?). After upgrading to Testing, the root partit
On 2020-08-18 11:27, Urs Thuermann wrote:
"Rick Thomas" writes:
The /dev/sdx names for devices have been unpredictable for quite a
while. Which one is sda and which sdb will depend on things like
timing -- which one gets recognized by the kernel first.
The best solution is to either use UUID
"Rick Thomas" writes:
> The /dev/sdx names for devices have been unpredictable for quite a
> while. Which one is sda and which sdb will depend on things like
> timing -- which one gets recognized by the kernel first.
>
> The best solution is to either use UUID or LABEL when you fsck
> and/or mo
Hi,
i wrote:
> > I only deem *UUID as safe,
Nicolas George wrote:
> UUID can get duplicated too. Just have somebody copy the whole block
> device with "good ol' dd".
Yes, sure. A HDD of mine got by the Debian installation 128 GPT slots of
128 bytes. So the primary GPT including "protective MBR"
On 8/17/20 9:01 PM, hobie of RMN wrote:
On 2020-08-17 16:42, hobie of RMN wrote:
Hi, All -
My brother has been issuing "mount /dev/sdb1" prior to backing up some
files to a second hard disk. He lately upgraded to 'testing', and it
appears (from result of running df) that what the system now ca
Thomas Schmitt (12020-08-18):
> I only deem *UUID as safe, unless the same names on different devices
> are intented and always only one of those devices will be connected.
UUID can get duplicated too. Just have somebody copy the whole block
device with "good ol' dd".
Regards,
--
Nicolas Geor
Hi,
didier gaumet wrote:
> give a name to the underlyning [GPT] partition
Let me add the hint that a GPT partition "name" is a user defined string
(in fstab and lsblk: PARTLABEL=) whereas the partition UUIDs in GPT
get handed out by partition editors automatically as random data
(human readable a
On Mon, Aug 17, 2020, at 4:42 PM, hobie of RMN wrote:
> Hi, All -
>
> My brother has been issuing "mount /dev/sdb1" prior to backing up some
> files to a second hard disk. He lately upgraded to 'testing', and it
> appears (from result of running df) that what the system now calls
> /dev/sdb1 is w
Hello,
Apparently, it is also possible to either:
- give a name to the filesystem (use e2label to do so, the filesystem being
ext4) and mount the filesystem by using this name as a parameter of the mount
command instead of /dev/sd* or an UUID
- give a name to the underlyning partition (use par
On 8/18/2020 6:01 AM, hobie of RMN wrote:
On 2020-08-17 16:42, hobie of RMN wrote:
Hi, All -
My brother has been issuing "mount /dev/sdb1" prior to backing up some
files to a second hard disk. He lately upgraded to 'testing', and it
appears (from result of running df) that what the system now
> On 2020-08-17 16:42, hobie of RMN wrote:
>> Hi, All -
>>
>> My brother has been issuing "mount /dev/sdb1" prior to backing up some
>> files to a second hard disk. He lately upgraded to 'testing', and it
>> appears (from result of running df) that what the system now calls
>> /dev/sdb1 is what he
On 2020-08-17 16:42, hobie of RMN wrote:
Hi, All -
My brother has been issuing "mount /dev/sdb1" prior to backing up some
files to a second hard disk. He lately upgraded to 'testing', and it
appears (from result of running df) that what the system now calls
/dev/sdb1 is what he has thought of a
On 13/11/13 18:09, Tixy wrote:
> On Wed, 2013-11-13 at 10:37 +1100, Scott Ferguson wrote:
>> On 13/11/13 01:40, Andre Majorel wrote:
> [...]
>>> Unfortunately, GNU dd does not have a --progress option but last
>>> time I looked, it responded to signal USR1 by writing its
>>> current stats on stderr
On Wed, 2013-11-13 at 10:37 +1100, Scott Ferguson wrote:
> On 13/11/13 01:40, Andre Majorel wrote:
[...]
> > Unfortunately, GNU dd does not have a --progress option but last
> > time I looked, it responded to signal USR1 by writing its
> > current stats on stderr. So you can use ps to find out the
On 13/11/13 01:40, Andre Majorel wrote:
> On 2013-11-11 15:06 +0100, berenger.mo...@neutralite.org wrote:
>
>> I do not remember having seen so much unused space on first disk.
>> Could dd have written stuff there, when I only asked it to read
>> there?
>
> dd writing to the argument of if= would
> On November 12, 2013 at 9:40 AM Andre Majorel wrote:
>
> Unfortunately, GNU dd does not have a --progress option but last
> time I looked, it responded to signal USR1 by writing its
> current stats on stderr. So you can use ps to find out the PID
> of your dd(1) process then kill -USR1 from ti
On 2013-11-11 15:06 +0100, berenger.mo...@neutralite.org wrote:
> I do not remember having seen so much unused space on first disk.
> Could dd have written stuff there, when I only asked it to read
> there?
dd writing to the argument of if= would be a bug. A major one.
> 2: the 2 disks are USB d
On Mon, Nov 11, 2013 at 03:06:44PM +0100, berenger.mo...@neutralite.org wrote:
> Hello.
>
> Few days ago, I tried to clone a damaged[1] disk to another one, of
> the same size, with dd.
> I had to interrupt the copy after more than 24 hours, because it was
> obviously too long[2].
Have you looked
On Mon, Nov 11, 2013 at 7:06 AM, wrote:
> Hello.
>
> Few days ago, I tried to clone a damaged[1] disk to another one, of the
> same size, with dd.
> I had to interrupt the copy after more than 24 hours, because it was
> obviously too long[2].
>
> Now, I am trying to look anew how to do the copy,
michael a écrit :
[...]
and I'm not sure what that means.
I'll welcome advice on whether it's the HDD about to die or whether the
interrupt/timed out messages indicate something else?
IMHO, that means you should begin to double check your backups. And
secondly, if I were at your place, I would
On Thursday 14 August 2008 21:58, michael wrote:
> A couple of weeks ago, 'smart' sent me:
>
> The following warning/error was logged by the smartd daemon:
> Device: /dev/hdb, not capable of SMART self-check
>
> and in /var/log/messages for that time I see (exc iptables info):
>
> Jul 30 05:13:10 r
dmesg | grep "hd" | wc -l
untested.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Oct 02, 2007 at 04:50:23PM +0200, Ivan Glushkov wrote:
> a simple question: Is there a way under linux, as a user (i.e. without
> superuser privileges) to find out how many hard drives are physically
> connected on the computer? I am not interested in the info given by
> /etc/fstab or by
On Tue, 02 Oct 2007 16:50:23 +0200
Ivan Glushkov <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> a simple question: Is there a way under linux, as a user (i.e.
> without superuser privileges) to find out how many hard drives are
> physically connected on the computer? I am not interested in the info
> g
On Tue, May 11 at 15:35, Antony Gelberg wrote:
One thing I did notice is that the disks were rather hot, abnormally imo.
The server is hardly stressed, as it's pretty much providing DNS, SMTP,
and IMAP for all of one user! :) Motherboard is an ASUS A7N8X.
What I am wondering is, is there some typ
hi ya alex
On Wed, 12 May 2004, Alex Malinovich wrote:
> On Wed, 2004-05-12 at 18:29, Alvin Oga wrote:
...
> > http://directron.com/hdcoolers.html
> >
> > if there is not say 1" of air clearance above the fans, the fans are just
> > noise makers
>
> There's ABOUT an inch of space between the
On Wed, 2004-05-12 at 18:29, Alvin Oga wrote:
> On Wed, 12 May 2004, Alex Malinovich wrote:
>
> > On Tue, 2004-05-11 at 23:35, David Cunningham wrote:
> > > Sounds good. What brand and model of heatsink do you use?
>
> http://directron.com/hdcoolers.html
>
> if there is not say 1" of air cleara
On Wed, 12 May 2004, Alex Malinovich wrote:
> On Tue, 2004-05-11 at 23:35, David Cunningham wrote:
> > Sounds good. What brand and model of heatsink do you use?
http://directron.com/hdcoolers.html
if there is not say 1" of air clearance above the fans, the fans are just
noise makers
have fun
On Tue, 2004-05-11 at 23:35, David Cunningham wrote:
> Sounds good. What brand and model of heatsink do you use?
Umm, to be honest, I'm not sure. :) They're copper, the size of a HD,
and have 2 fans on them. I can go by the shop where I got them tomorrow
and see if they still have the same ones.
> On Tue, 2004-05-11 at 09:35, Antony Gelberg wrote:
>> Hi all,
>>
>> I've recently built my first ever server with a pre-compiled kernel
>> (2.6.4
>> from backports.org). I had two 160GB SATA disks which both failed after
>> only
>> a couple of months. I found this extremely strange, unless they
On Tue, May 11, 2004 at 03:35:29PM +0100, Antony Gelberg wrote:
> Hi all,
>
> I've recently built my first ever server with a pre-compiled kernel (2.6.4
> from backports.org). I had two 160GB SATA disks which both failed after only
> a couple of months. I found this extremely strange, unless the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antony Gelberg <[EMAIL PROTECTED]> writes:
> One thing I did notice is that the disks were rather hot, abnormally
> imo.
Have you ever felt a hard drive that's been running for a long time
without stopping? They get hot! It's a moving part, and it
hi ya anthony/alex
On Tue, 11 May 2004, Alex Malinovich wrote:
> On Tue, 2004-05-11 at 09:35, Antony Gelberg wrote:
...
> > One thing I did notice is that the disks were rather hot, abnormally imo.
...
> I'm guessing you're using 7200 RPM or better disks. I've never seen a
> 7200 RPM disk t
On Tue, 2004-05-11 at 09:35, Antony Gelberg wrote:
> Hi all,
>
> I've recently built my first ever server with a pre-compiled kernel (2.6.4
> from backports.org). I had two 160GB SATA disks which both failed after only
> a couple of months. I found this extremely strange, unless they were
> from
46 matches
Mail list logo
