Hi
As you maintain libblkid, I'd like to ask - would it be possible to add
detection of filesystem block size to it? libblkid already has description
of various filesystem superblocks, so it shouldn't be too hard.
LVM needs to know the block size because when it enables caching for a
logical
On Wed, Oct 3, 2018 at 3:47 PM Joe Thornber wrote:
>
> On Wed, Oct 03, 2018 at 03:13:36PM +0100, Thanos Makatos wrote:
> > > Could you say more about why you want to do this?
> > >
> >
> > So that I can directly read the data block without having to pass through
> > dm-thin, e.g. there might be a
On Wed, Oct 03, 2018 at 03:13:36PM +0100, Thanos Makatos wrote:
> > Could you say more about why you want to do this?
> >
>
> So that I can directly read the data block without having to pass through
> dm-thin, e.g. there might be a more direct datapath to the physical block
> device.
>
>
> Could you say more about why you want to do this?
>
So that I can directly read the data block without having to pass through
dm-thin, e.g. there might be a more direct datapath to the physical block
device.
Mappings don't change if you're not using snapshots. If you are, then any
> write
>
On Wed, Oct 03, 2018 at 01:40:22PM +0100, Thanos Makatos wrote:
> I have a kernel module that sits on top of a thin device mapper target that
> receives block I/O requests and re-submits then to the thin target. I would
> like to implement the following functionality: whenever I receive a write
>
