On Sun, 28 Mar 2021 at 21:51, Tim via users
wrote:
> On Sun, 2021-03-28 at 19:30 -0300, George N. White III wrote:
> > There have also been efforts to predict eminent drive failure (e.g.,
> > using S.M.A.R.T) but without much success.
>
> It took me a moment to wonder what would be
On Mon, Mar 29, 2021 at 7:17 AM Richard Shaw wrote:
>
> So after about 12 forced power offs while copying data (via rsync) this is
> the only output from dmesg:
>
> # dmesg | grep -i btrfs
> [0.776375] Btrfs loaded, crc32c=crc32c-generic, zoned=yes
> [5.497241] BTRFS: device fsid
So after about 12 forced power offs while copying data (via rsync) this is
the only output from dmesg:
# dmesg | grep -i btrfs
[0.776375] Btrfs loaded, crc32c=crc32c-generic, zoned=yes
[5.497241] BTRFS: device fsid d9a2a011-77a2-43be-acd1-c9093d32125b
devid 1 transid 389 /dev/sdc scanned
On Sun, Mar 28, 2021 at 6:51 PM Tim via users
wrote:
>
> I'm recently seeing info like this in logwatch emails:
>
> **Unmatched Entries**
> Device: /dev/sda [SAT], CHECK POWER STATUS spins up disk (0x81 ->
> 0xff)
>
> Which makes little sense to me. The system is a 24/7 server,
On Sun, Mar 28, 2021 at 4:31 PM George N. White III wrote:
>
> Your plan needs to consider backups and/or replication (to cloud or another
> site).It is easy and cheap to lose data. Not losing data is not easy and
> not cheap.
Exactly this. If the data is important, it's backed up. If
On Sun, Mar 28, 2021 at 11:47 AM Richard Shaw wrote:
>
> I appreciate all the detailed response, but at the same time the answers seem
> often bi-polar... You can do all these great things with BTRFS! But even if
> you test your raid array multiple times, a bad firmware may still eat all
>
On Sun, 2021-03-28 at 19:30 -0300, George N. White III wrote:
> There have also been efforts to predict eminent drive failure (e.g.,
> using S.M.A.R.T) but without much success.
It took me a moment to wonder what would be famous/respected about
drive failures. ;-) But I've often wondered if
On Sun, 28 Mar 2021 at 14:47, Richard Shaw wrote:
> Ok, so I'm struggling a bit here :)
>
> I appreciate all the detailed response, but at the same time the answers
> seem often bi-polar... You can do all these great things with BTRFS! But
> even if you test your raid array multiple times, a bad
On Fri, Mar 26, 2021 at 9:41 AM Chris Murphy
wrote:
> On Thu, Mar 25, 2021 at 6:00 AM Richard Shaw wrote:
> >
> > So how long do you wait until you consider the drive "good"? :)
> >
> > I'm not in a hurry so I could setup two of the drives in a RAID1 mirror
> and copy my media over and just let
On Thu, Mar 25, 2021 at 6:00 AM Richard Shaw wrote:
>
> So how long do you wait until you consider the drive "good"? :)
>
> I'm not in a hurry so I could setup two of the drives in a RAID1 mirror and
> copy my media over and just let it run for a while before I add disks 3 & 4.
We don't have
Make sure to get NAS type drives. The non-Enterprise, Non-Nas drives
usually won't timeout for 2-3 minutes.The NAS drives typically can
be set 7 seconds or less. You also want to evaluate setting the
timeout lower. And watch out for the SMR disks, get CMR ones. The
SMR's are said to suck
On Wed, Mar 24, 2021 at 11:26 PM Chris Murphy
wrote:
> On Wed, Mar 24, 2021 at 3:47 PM Richard Shaw wrote:
> >
> > I've been running MythTV for about 10 years now and I've finally
> outgrown my media storage, currently a single 4TB disk drive. I have
> purchased 3 additional drives of the same
On Wed, Mar 24, 2021 at 3:47 PM Richard Shaw wrote:
>
> I've been running MythTV for about 10 years now and I've finally outgrown my
> media storage, currently a single 4TB disk drive. I have purchased 3
> additional drives of the same model and plan to put them into a BTRFS RAID1
> array.
>
>
I've been running MythTV for about 10 years now and I've finally outgrown
my media storage, currently a single 4TB disk drive. I have purchased 3
additional drives of the same model and plan to put them into a BTRFS RAID1
array.
Setting nodatacow on the media directories is a no-brainer, but what
14 matches
Mail list logo
