Re: [git pull] device mapper fix for 4.18-rc6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Fri, 20 Jul 2018, Mike Snitzer wrote:

> On Fri, Jul 20 2018 at  5:25pm -0400,
> Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> > On Fri, Jul 20, 2018 at 12:14 PM Mike Snitzer <snitzer@xxxxxxxxxx> wrote:
> > >
> > >   Fix DM writecache target to allow an optional offset to the start of
> > >   the data and metadata area.  This allows userspace tools (e.g. LVM2)
> > >   to place a header and metadata at the front of the writecache device
> > >   for its use.
> > 
> > "fix"?
> > 
> > Not really.
> 
> I hold it to be a "fix" because it was an embarassing oversight on my
> part.  Without this, userspace support cannot be properly added.  LVM2
> developers raised their inability to put their metadata anywhere and I
> was like "oh shit".

This is not oversight.

It was originally planned that the dm-writecache target would use lvm 
metadata just like the dm-cache target - if it were implemented this way, 
no "offset" argument would be needed. But David Teigland who was given the 
task to implement dm-writecache support in lvm refused to do it this way 
and he insists that he must put some of his own metadata at the beginning 
of the cache device before the superblock.

So this patch is needed because of him.

Mikulas

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel



[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux