> -----Original Message-----
> From: linux-btrfs-ow...@vger.kernel.org [mailto:linux-btrfs-
> ow...@vger.kernel.org] On Behalf Of Christian
> Sent: Thursday, 18 June 2015 12:34 AM
> To: linux-btrfs@vger.kernel.org
> Subject: Re: trim not working and irreparable errors from btrfsck
>
> On 06/17/2015 10:22 AM, Chris Murphy wrote:
> > On Wed, Jun 17, 2015 at 6:56 AM, Christian Dysthe <cdys...@gmail.com>
> wrote:
> >> Hi,
> >>
> >> Sorry for asking more about this. I'm not a developer but trying to learn.
> >> In my case I get several errors like this one:
> >>
> >> root 2625 inode 353819 errors 400, nbytes wrong
> >>
> >> Is it inode 353819 I should focus on and what is the number after
> >> "root", in this case 2625?
> >
> > I'm going to guess it's tree root 2625, which is the same thing as fs
> > tree, which is the same thing as subvolume. Each subvolume has its own
> > inodes. So on a given Btrfs volume, an inode number can exist more
> > than once, but in separate subvolumes. When you use btrfs inspect
> > inode it will list all files with that inode number, but only the one
> > in subvol ID 2625 is what you care about deleting and replacing.
> >
> Thanks! Deleting the file for that inode took care of it. No more errors.
> Restored it from a backup.
>
> However, fstrim still gives me "0 B (0 bytes) trimmed, so that may be another
> problem. Is there a way to check if trim works?
I've got the same problem. I've got 2 SSDs with 2 partitions in RAID1, fstrim
always works on the 2nd partition but not the first. There are no errors on
either filesystem that I know of, but the first one is root so I can't take it
offline to run btrfs check.
Paul.
N�����r��y����b�X��ǧv�^�){.n�+����{�n�߲)����w* jg��� �����ݢj/���z�ޖ��2�ޙ����&�)ߡ�a���� �G���h��j:+v���w��٥
