On Fri, Jun 2, 2023 at 9:11?AM James <jam@tigger.ws> wrote:
>
>
> On 2 Jun 2023, at 8:59 pm, James Abernathy <jfabernathy@gmail.com> wrote:
>
>
>
> On Fri, Jun 2, 2023 at 8:33?AM James <jam@tigger.ws> wrote:
>
>>
>>
>> On 2 Jun 2023, at 8:08 pm, Richard Shaw <hobbes1069@gmail.com> wrote:
>>
>> On Fri, Jun 2, 2023 at 6:54?AM James <jam@tigger.ws> wrote:
>>
>>> There is quite a lot of discussion on why not to use btrfs with maria
>>> https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/58
>>>
>>
>> There's a few different solutions if you already have the files created
>> since the +C must be done at creation.
>>
>> My method is to:
>> mv <file> <file>_backup
>> touch <file>
>> chattr +C <file>
>> dd if=<file>_backup of=<file>
>>
>> You can add bytesize (bz=1M) or similar to speed it up. I did this with a
>> 1TB blockchain file successfully.
>>
>>
>> Mostly for Jim Abernathy's info, I pretty much stick to ext4, but was
>> toying with idea of changing
>>
>> James
>>
>
> I've used btrfs in a RAID 1 mirror array on my production backend with
> mariadb for a year plus a few months without issues. I update about once a
> month and that usually requires a reboot. The boot ssd also was installed
> with btrfs with timeshift snapshots every hour.
>
> I didn't do anything about COW disable at the time of install. I see from
> the archlinux link that someone said it was addressed 2 years ago??? If
> that's true, should I even need to worry about chattr +C <file>???
>
> I learned most of what I know about BTRFS usage from the Kubuntu Forum.
> They have a BTRFS category and I'll ask for knowledge over there.
>
> I make special arrangements for COW issues for Virtual Machines by keeping
> all qcow2 files on a separate ssd formatted ext4. I think that is required
> because qcow2 files already use COW. I prefer this instead of chattr +C
> /var/lib/libvirt/images. Using a separate ext4 ssd has the added benefit of
> not having to recreate VMs when I change Distro every month or so because
> some defect in my brain requires it.
>
>
> Jim if you uncover anything interesting please post it (or even just mail
> me)
> thanks
> James
>
It must be fixed. I did lsattr /var/lib/mysql/ and the whole directory has
the COW disabled:
[root@eos-mythtv-master mythtv]# lsattr /var/lib/mysql/
---------------C------ /var/lib/mysql/aria_log_control
---------------C------ /var/lib/mysql/aria_log.00000001
---------------C------ /var/lib/mysql/ibdata1
---------------C------ /var/lib/mysql/ib_logfile0
---------------C------ /var/lib/mysql/mysql
---------------C------ /var/lib/mysql/performance_schema
---------------C------ /var/lib/mysql/sys
---------------C------ /var/lib/mysql/mysql_upgrade_info
---------------C------ /var/lib/mysql/multi-master.info
---------------C------ /var/lib/mysql/ddl_recovery-backup.log
---------------C------ /var/lib/mysql/mythconverg
---------------C------ /var/lib/mysql/ib_buffer_pool
---------------C------ /var/lib/mysql/ddl_recovery.log
---------------C------ /var/lib/mysql/ibtmp1
---------------C------ /var/lib/mysql/eos-mythtv-master.pid