On Mon, Mar 11, 2024 at 9:13 AM Ming Lei wrote:
>
> On Sun, Mar 10, 2024 at 02:11:11PM -0400, Patrick Plenefisch wrote:
> > On Sun, Mar 10, 2024 at 11:27 AM Mike Snitzer wrote:
> > >
> > > On Sun, Mar 10 2024 at 7:34P -0400,
> > > Ming Lei wrote:
>
On Sun, Mar 10, 2024 at 11:27 AM Mike Snitzer wrote:
>
> On Sun, Mar 10 2024 at 7:34P -0400,
> Ming Lei wrote:
>
> > On Sat, Mar 09, 2024 at 03:39:02PM -0500, Patrick Plenefisch wrote:
> > > On Wed, Mar 6, 2024 at 11:00 AM Ming Lei wrote:
> >
On Wed, Mar 6, 2024 at 11:00 AM Ming Lei wrote:
>
> On Tue, Mar 05, 2024 at 12:45:13PM -0500, Mike Snitzer wrote:
> > On Thu, Feb 29 2024 at 5:05P -0500,
> > Goffredo Baroncelli wrote:
> >
> > > On 29/02/2024 21.22, Patrick Plenefisch wrote:
> > >
On Thu, Feb 29, 2024 at 2:56 PM Goffredo Baroncelli wrote:
>
> > Your understanding is correct. The only thing that comes to my mind to
> > cause the problem is asymmetry of the SATA devices. I have one 8TB
> > device, plus a 1.5TB, 3TB, and 3TB drives. Doing math on the actual
> > extents, lowerV
On Wed, Feb 28, 2024 at 2:19 PM Goffredo Baroncelli wrote:
>
> On 28/02/2024 18.25, Patrick Plenefisch wrote:
> > I'm unsure if this is just an LVM bug, or a BTRFS+LVM interaction bug,
> > but LVM is definitely involved somehow.
> > Upgrading from 5.10 to 6.1, I noti
I'm unsure if this is just an LVM bug, or a BTRFS+LVM interaction bug,
but LVM is definitely involved somehow.
Upgrading from 5.10 to 6.1, I noticed one of my filesystems was
read-only. In dmesg, I found:
BTRFS error (device dm-75): bdev /dev/mapper/lvm-brokenDisk errs: wr
0, rd 0, flush 1, corrup
