On 2021/2/20 下午8:07, chainofflowers wrote:
On 20.02.21 12:46, Forza wrote:
Are you using fstrim by any chance? Could the problem be related to
https://patchwork.kernel.org/project/fstests/patch/20200730121735.55389-1-...@suse.com/
Yes, that's what I mentioned in my first post.
Actually, it
On 20.02.21 12:46, Forza wrote:
> Are you using fstrim by any chance? Could the problem be related to
> https://patchwork.kernel.org/project/fstests/patch/20200730121735.55389-1-...@suse.com/
Yes, that's what I mentioned in my first post.
Actually, it all started with the bug with dm, but some si
On 2021-02-08 22:05, chainofflowers wrote:
Hi Qu!
It happened again, and this time I've been able to dump the dmesg.
Also this time it happened on my home drive, please see the attached dump.
What can I do to fix it?
btrfs scrub reports no error, neither does brfs check.
I have also remounte
On 2021/2/20 下午7:26, chainofflowers wrote:
Hi Qu!
Is there any chance to find some hints of the issue in the log I attached?
Sorry for the late reply.
The weird part is, the access beyond boundary happens for read, no
wonder why previously added debug for discard doesn't work.
Currently I
Hi Qu!
Is there any chance to find some hints of the issue in the log I attached?
On 08.02.21 22:05, chainofflowers wrote:
> Hi Qu!
>
> It happened again, and this time I've been able to dump the dmesg.
> Also this time it happened on my home drive, please see the attached dump.
>
> What can I
Hi Qu!
It happened again, and this time I've been able to dump the dmesg.
Also this time it happened on my home drive, please see the attached dump.
What can I do to fix it?
btrfs scrub reports no error, neither does brfs check.
I have also remounted the partition with -oclear_cache,space_cache,
On 2021/1/22 上午7:55, chainofflowers wrote:
Hi Qu,
it happened again. This time on my /home partition.
I rebooted from an external disk and ran btrfs check without first going
through btrfs scrub, and this is the output, no errors:
--
[manjaro oc]# btrf
Hi Qu,
it happened again. This time on my /home partition.
I rebooted from an external disk and ran btrfs check without first going
through btrfs scrub, and this is the output, no errors:
--
[manjaro oc]# btrfs check /dev/mapper/OMO
Opening filesystem to ch
Thanks, I put everything in place... I am now waiting for the next
occurrence...
> The best way to debug such problem is to recompile the kernel adding
> some debug outputs.
> (Maybe it can be done with bpftrace, but not yet familiar with that)
>
> If you're able to recompile the kenerl (using abs
On 2021/1/18 上午7:38, chainofflowers wrote:
Hi all,
Hi Qu,
I am also getting this very same error on my system.
Actually, I am experiencing this since the following old bug was introduced AND
also even after it has been fixed:
https://lore.kernel.org/linux-btrfs/20190521190023.GA68070@glet/T/
Hi all,
Hi Qu,
I am also getting this very same error on my system.
Actually, I am experiencing this since the following old bug was introduced AND
also even after it has been fixed:
https://lore.kernel.org/linux-btrfs/20190521190023.GA68070@glet/T/
That (dm-related) bug was claimed to have been
On Wed, Feb 24, 2016 at 09:58:08AM +0100, Szalma László wrote:
> - echo 3 > /proc/sys/vm/drop_cachessometimes fixes the problem, but not
> every time
Interesting. I just had the issue happen with one of my files, tried
this, and it's now readable again.
--
To unsubscribe from this list: send t
On Tue, Feb 23, 2016 at 09:37:03PM -0700, Chris Murphy wrote:
> On Tue, Feb 23, 2016 at 8:02 PM, Kenny MacDermid
> wrote:
>
> >
> > rw,noatime,compress=lzo,ssd,discard,space_cache,autodefrag,inode_cache
>
> It sounds like an ssd trim bug. I'd check the firmware for updates. If
> it's up to date,
2016-02-24 05:37 keltezéssel, Chris Murphy írta:
On Tue, Feb 23, 2016 at 8:02 PM, Kenny MacDermid
wrote:
rw,noatime,compress=lzo,ssd,discard,space_cache,autodefrag,inode_cache
It sounds like an ssd trim bug. I'd check the firmware for updates. If
it's up to date, I'd drop discard mount option
On Tue, Feb 23, 2016 at 8:02 PM, Kenny MacDermid
wrote:
>
> rw,noatime,compress=lzo,ssd,discard,space_cache,autodefrag,inode_cache
It sounds like an ssd trim bug. I'd check the firmware for updates. If
it's up to date, I'd drop discard mount option first and try to
reproduce. Or just use the def
On Tue, Feb 23, 2016 at 05:56:58PM -0800, Marc MERLIN wrote:
> On Tue, Feb 23, 2016 at 08:40:46PM -0400, Kenny MacDermid wrote:
> > I'm running btrfs on DM-Crypt Luks running on LVM.
> >
> > Occasionally I get files that are unreadable for some period of time.
> > Attempting to read from them resu
On Tue, Feb 23, 2016 at 08:40:46PM -0400, Kenny MacDermid wrote:
> I'm running btrfs on DM-Crypt Luks running on LVM.
>
> Occasionally I get files that are unreadable for some period of time.
> Attempting to read from them results in an
>
> Input/output error
>
> Sometimes they'll come back on
I'm running btrfs on DM-Crypt Luks running on LVM.
Occasionally I get files that are unreadable for some period of time.
Attempting to read from them results in an
Input/output error
Sometimes they'll come back on their own, and sometimes a scrub seems to
help, but sometimes I just have to dele
Original Message
Subject: corruption, bad block, input/output errors - do i run --repair?
From: Matt McKinnon
To:
Date: 2014年11月07日 22:33
Hi All,
I'm running into some corruption and I wanted to seek out advice on
whether or not to run btrfs check --repair, or if I s
Matt McKinnon posted on Fri, 07 Nov 2014 09:33:44 -0500 as excerpted:
> I'm running into some corruption and I wanted to seek out advice on
> whether or not to run btrfs check --repair, or if I should fall back to
> my backup file server, or both.
>
> The system is mountable, and usable.
>
> # u
Hi All,
I'm running into some corruption and I wanted to seek out advice on
whether or not to run btrfs check --repair, or if I should fall back to
my backup file server, or both.
The system is mountable, and usable.
# uname -a
Linux cbmm-fs 3.17.2-custom #1 SMP Thu Oct 30 14:09:57 EDT 2014
21 matches
Mail list logo
