On 2018-02-19 13:29, Anand Jain wrote:
On 02/14/2018 10:19 PM, Tomasz Chmielewski wrote:
Just FYI, how dangerous running btrfs can be - we had a fatal,
unrecoverable MySQL corruption when btrfs decided to do one of these
"I have ~50 GB left, so let's do out of space (and corrupt some files
at
On 02/14/2018 10:19 PM, Tomasz Chmielewski wrote:
Just FYI, how dangerous running btrfs can be - we had a fatal,
unrecoverable MySQL corruption when btrfs decided to do one of these "I
have ~50 GB left, so let's do out of space (and corrupt some files at
the same time, ha ha!)".
Thanks for
On 15.02.2018 09:17, Tomasz Chmielewski wrote:
> On 2018-02-15 16:02, Tomasz Chmielewski wrote:
>> On 2018-02-15 13:32, Qu Wenruo wrote:
>>
>>> Is there any kernel message like kernel warning or backtrace?
>>
>> I see there was this one:
>>
>> Feb 13 13:53:32 lxd01 kernel: [9351710.878404] --
Tomasz Chmielewski posted on Thu, 15 Feb 2018 16:02:59 +0900 as excerpted:
>> Not sure if the removal of 80G has anything to do with this, but this
>> seems that your metadata (along with data) is quite scattered.
>>
>> It's really recommended to keep some unallocated device space, and one
>> of
On 2018年02月15日 15:02, Tomasz Chmielewski wrote:
> On 2018-02-15 13:32, Qu Wenruo wrote:
>
>> Is there any kernel message like kernel warning or backtrace?
>
> I see there was this one:
>
> Feb 13 13:53:32 lxd01 kernel: [9351710.878404] [ cut
> here ] Feb 13 13:53:32 lxd
On 2018-02-15 16:02, Tomasz Chmielewski wrote:
On 2018-02-15 13:32, Qu Wenruo wrote:
Is there any kernel message like kernel warning or backtrace?
I see there was this one:
Feb 13 13:53:32 lxd01 kernel: [9351710.878404] [ cut here
]
Feb 13 13:53:32 lxd01 kernel: [9351
On 2018-02-15 13:32, Qu Wenruo wrote:
Is there any kernel message like kernel warning or backtrace?
I see there was this one:
Feb 13 13:53:32 lxd01 kernel: [9351710.878404] [ cut here
]
Feb 13 13:53:32 lxd01 kernel: [9351710.878430] WARNING: CPU: 9 PID: 7780
at /home
On 2018年02月15日 12:19, Tomasz Chmielewski wrote:
> On 2018-02-15 10:47, Qu Wenruo wrote:
>> On 2018年02月14日 22:19, Tomasz Chmielewski wrote:
>>> Just FYI, how dangerous running btrfs can be - we had a fatal,
>>> unrecoverable MySQL corruption when btrfs decided to do one of these "I
>>> have ~50 GB
On 2018-02-15 10:47, Qu Wenruo wrote:
On 2018年02月14日 22:19, Tomasz Chmielewski wrote:
Just FYI, how dangerous running btrfs can be - we had a fatal,
unrecoverable MySQL corruption when btrfs decided to do one of these
"I
have ~50 GB left, so let's do out of space (and corrupt some files at
the
On 2018年02月14日 22:19, Tomasz Chmielewski wrote:
> Just FYI, how dangerous running btrfs can be - we had a fatal,
> unrecoverable MySQL corruption when btrfs decided to do one of these "I
> have ~50 GB left, so let's do out of space (and corrupt some files at
> the same time, ha ha!)".
I'm recent
Tomasz Chmielewski posted on Wed, 14 Feb 2018 23:19:20 +0900 as excerpted:
> Just FYI, how dangerous running btrfs can be - we had a fatal,
> unrecoverable MySQL corruption when btrfs decided to do one of these "I
> have ~50 GB left, so let's do out of space (and corrupt some files at
> the same t
Just FYI, how dangerous running btrfs can be - we had a fatal,
unrecoverable MySQL corruption when btrfs decided to do one of these "I
have ~50 GB left, so let's do out of space (and corrupt some files at
the same time, ha ha!)".
Running btrfs RAID-1 with kernel 4.14.
Tomasz Chmielewski
htt
12 matches
Mail list logo
