On Wed, Oct 03, 2018 at 09:56:13AM +, Michael Firth wrote:
> >
> > As far as I know, if 'btrfs check' is clean then you're in the clear for
> > any known
> > issues involving the fs structure. Of course, a 'btrfs scrub' is necessary
> > to
> > check for data and metadata corruption...
Hi Hans,
On Wed, Oct 03, 2018 at 12:05:31AM +0200, Hans van Kranenburg wrote:
> Hi,
>
> On 10/02/2018 10:08 PM, Nicholas D Steeves wrote:
> > Hi Michael,
> >
> > On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
> >>
> >> BTRFS may not be a filesystem that everyone uses, but I feel
Hi,
> -Original Message-
>
> Hi Michael,
>
> On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
> >
> > After this, there was a file that was errored on the filesystem (as
> > reported by 'btrfs check'), and it seems BTRFS doesn't have any tools
> > to resolve the error.
Hi,
On 10/02/2018 10:08 PM, Nicholas D Steeves wrote:
> Hi Michael,
>
> On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
>>
>> After this, there was a file that was errored on the filesystem (as
>> reported by 'btrfs check'), and it seems BTRFS doesn't have any tools to
>> resolve
Hi Michael,
On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
>
> After this, there was a file that was errored on the filesystem (as
> reported by 'btrfs check'), and it seems BTRFS doesn't have any tools to
> resolve the error. Deleting the file at the reported inode has cleared
>
Package: src:linux
Version: 4.9.110-3+deb9u4
Severity: important
Dear Maintainer,
While extracting files over NFS into a BTRFS file system a kernel bug
report was triggered. I don't believe the bug is related to the fact
that the access was over NFS, but should declare that just in case.
After
6 matches
Mail list logo
