- #DRIVECLONE 11 WORKSTATIOIN FAILED TO RESTORE DISK LAYOUT DRIVER#
- #DRIVECLONE 11 WORKSTATIOIN FAILED TO RESTORE DISK LAYOUT WINDOWS#
And as the block size is going to be 4KiB, there's no point in having more inodes created than files.Įven moderate use of containers with overlayfs dramatically increases inode consumption Mkfs.ext4 -i 4096 or mkfs.ext4 -T news will do it. I think it's a big enough hassle that we should just change the inode ratio for Fedora 31, because the work around is to tell people to reinstall, and either pick another file sytsem or modify /etc/nf before reinstalling to alter the default inode ratio so that Anaconda will pick it up at mkfs time. And podman by default does use overlayfs.ĬoreOS made this change almost four years ago when they were using ext4. This is one of the reasons many container centric projects have moved to XFS and Btrfs which have dynamic inode allocation and reflinks. On ext4 the ratio can only be set at mkfs time. Inode exhaustion is somewhat common with the default ext4 inode ratio, 1 per 16KiB, where typical inode consumption in container centric workflows is 1 per ~6KiB.
#DRIVECLONE 11 WORKSTATIOIN FAILED TO RESTORE DISK LAYOUT DRIVER#
It's not possible to use the original, deprecated, Docker overlay driver in Podman, near as I can your podman comment in #104 made me think of an old problem.Įven moderate use of containers with overlayfs dramatically increases inode consumption. UPDATE: This problem is substantially reduced by the Docker overlay2 driver which Podman is using, but calls it overlay. Anyone who wants it can do a custom install.įedora-Workstation-netinst-x86_64-29_Beta: root volume uses ~5.1Gįedora-Silverblue-ostree-x86_64-29: root volume uses ~3.8G (one tree, two trees might approach 5.1G depending on the diff between them)ĥ0G is a decent chunk of space, not sure where it's all going. If you combine root and home, you could keep LVM but it's sorta pointless. If you drop LVM, I think you must combine root and home, because without LVM it's non-trivial, risky, and takes a long time (possibly hours) to shrink home and grow root. big root volume with /home as a directory. 8G swapfile vs 8G swap partition (or LV) is still gonna require an 8G reservation either way. However, I'm not super clear on the advantage over a dedicated swap partition. Supporting file based swap on such storage is possible with a loop or nbd device. Swapfiles * can't directly be supported on COW storage, which includes Btrfs, XFS (reflinks), anything on dm-thin, including Stratis. That'll pilfer it from the home volume at installation time.īoot * is still needed for encrypted root alternative is GRUB and Anaconda work to use GRUB's built in LUKS support and make it look somewhat pretty at boot time (now that we're hiding GRUB). Simplest solution is boost root volume max from 50G to e.g. Actually, fwupd helps here: bugs are fixed with firmware updates, but also getting Fedora users with a given make/model all on the same firmware revision helps too.ĭefault partitioning. And if anything breaks the broad user case, there's a release criterion that'd make it a blocking bug.
#DRIVECLONE 11 WORKSTATIOIN FAILED TO RESTORE DISK LAYOUT WINDOWS#
The Windows bootloader is oblivious to our layout. Dual boot will not be negatively impacted.