Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 563316 - sys-fs/lvm2 cannot create cache volumes without USE=+thin
Summary: sys-fs/lvm2 cannot create cache volumes without USE=+thin
Status: IN_PROGRESS
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Robin Johnson
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-17 13:49 UTC by Jan Psota
Modified: 2016-03-20 17:14 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Psota 2015-10-17 13:49:15 UTC
x6 ~ # lvconvert -y --type cache-pool --poolmetadata vga/cachemeta vga/cachedata
  WARNING: Unrecognised segment type cache-pool
  Invalid argument for --type: cache-pool
  Error during parsing of command line.

After changing --with-cache=none to ...=internal in line 144 of ebuild:
                myconf="${myconf} --with-thin=none --with-cache=internal"

# lvconvert -y --type cache-pool --poolmetadata vga/cachemeta vga/cachedata
 [...]  Converted vga/cachedata to cache pool.

Enabling +thin useflag would pull dev-libs/boost and it's an ostentation ;-)

Conclusion:
execute sed -i 's/\(with-cache=\)none/\1internal/'
on sys-fs/lvm ebuilds

Package grows 21KB/4M on amd64, setting with-cache=shared does not do the job.
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2015-11-02 19:18:19 UTC
If you simply change cache=none -> cache=internal, but do NOT have the cache_* binaries from thin-provisioning-tools, you're risking having problems in future.

agk: as upstream, would you consider having cache=internal, but NOT the thin tools present to be a supported configuration?
Comment 2 Jan Psota 2015-11-02 20:26:06 UTC
> agk: as upstream, would you consider having cache=internal, but NOT the thin
> tools present to be a supported configuration?

Of course! I only don't want dev-libs/boost to take 110MB disk space (and 0.5h compilation...) on "thin" rescue system but still have cache support working. And it works like magic :-)
Comment 3 Doug Goldstein gentoo-dev 2016-03-20 15:45:58 UTC
(In reply to Robin Johnson from comment #1)
> If you simply change cache=none -> cache=internal, but do NOT have the
> cache_* binaries from thin-provisioning-tools, you're risking having
> problems in future.
> 
> agk: as upstream, would you consider having cache=internal, but NOT the thin
> tools present to be a supported configuration?

Robin: any feedback here?
Comment 4 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2016-03-20 17:14:44 UTC
(In reply to Doug Goldstein from comment #3)
> (In reply to Robin Johnson from comment #1)
> > If you simply change cache=none -> cache=internal, but do NOT have the
> > cache_* binaries from thin-provisioning-tools, you're risking having
> > problems in future.
> > 
> > agk: as upstream, would you consider having cache=internal, but NOT the thin
> > tools present to be a supported configuration?
> 
> Robin: any feedback here?

I didn't hear anything back from agk at all.