Re:We saved millions in SSD costs by upgrading our filesystem
by notacoward on Tuesday November 09, 2021 @01:15PM
(#29165195)
The fact that there's two layers both doing this kind of thing (especially oblivious to one another) is a known and studied issue. Most of that study has been in the context of virtual-machine filesystems atop host filesystems but it's also applicable here. I'm pretty sure there was a paper at FAST about this several years ago, but can't find it right now. It's entirely likely that COW-over-COW is a bad choice just like TCP-over-TCP is.
[ Parent
| on HN ]
Re:We saved millions in SSD costs by upgrading our filesystem
by klodolph on Tuesday November 09, 2021 @01:25PM
(#29165337)
Are you thinking of the classic, "Don't Stack Your Log On My Log"?
https://www.usenix.org/conference/inflow14/workshop-program/...
Re:We saved millions in SSD costs by upgrading our filesystem
by notacoward on Tuesday November 09, 2021 @03:37PM
(#29167126)
Yeah, seems about right. Thanks!
Re:We saved millions in SSD costs by upgrading our filesystem
by the8472 on Tuesday November 09, 2021 @03:03PM
(#29166727)
But the upper-level CoW can coordinate with the lower level via TRIM, that's not quite the same as TCP-in-TCP where the congestion algorithms don't talk to each other.
Re:We saved millions in SSD costs by upgrading our filesystem
by notacoward on Tuesday November 09, 2021 @03:38PM
(#29167136)
Yes, TRIM exists, but it's a very limited form of coordination at best and implementations don't even do all they can with that. Every analogy is imperfect.