Comment 3 for bug 1974100
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: inode lazy init in a VM fills virtual disk with garbage | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi Brent,
thank you for all the detail and dedication already spent on this!
Just to be sure as there are two theories up for discussion:
1. ext4lazyinit fills it all
2. gns3 with discard=on fills it all due to maybe DISCARD being ignored
I was reading through the links and discussions and I wanted to ask to maybe cut this down to just one thing to talk about.
The references about early/lazy ext init indicate that no matter if done early or late you'd only loose the "normal" inode overhead which is usually <2%. So while you might see this laze init working and filling a few I'd not expect it to fill it massively.
Can you confirm that?
If so, we can kind of ignore this aspect other than hinting the team that builds the images to consider using "assume_
If so we could then focus solely on #2 if and why discards are being ignored.
OTOH If I read this right, you said sized to 1TB.
So if we assume 1.5% usual inode overhead that would already be ~15G right.
So even more - are we talking about the try to have less inode init or about a lack of proper DISCARD handling?