Rich Freeman wrote: > On Fri, May 22, 2020 at 12:15 PM Dale <rdalek1...@gmail.com> wrote: >> The thing about the one I have now in use by LVM for /home, one is SMR and >> one is PMR. Even if the OS is aware, does it even know which drive the data >> is going to end up being stored on? I'm pretty sure since the PMR drive was >> in use before the SMR that the PMR is likely full. From my understanding, >> LVM doesn't balance the data out. It will fill up a drive and then move on >> to the next. If you add another, it will fill up the 2nd drive and then >> start on the newly added drive. Maybe it does do some magic but does the OS >> know which drive data is going to hit? >> > So, as far as I'm aware nothing on linux is natively optimized for > SMR. I'm sure some people use host-managed SMR drives on linux for > application-specific writing, but they're probably writing raw blocks > without using a filesystem. > > However, if anything was going to be made SMR-aware then it would have > to be implemented at all block layers, just like barrier support. I > think back in the early days of barrier support some layers didn't > support it, and a barrier can only make it from the filesystem to the > drive if it is implemented in lmv+mdadm+driver and so on. > > If somebody added SMR support to ext4 but not to LVM then ext4 > wouldn't detect the LV as an SMR drive, because lvm wouldn't pass that > through. > > I suspect sooner or later a solution will emerge, but it could be a > while. I suspect any solution would be for drives that could be set > to be host-managed, because otherwise you're working around an extra > layer of obfuscation. Maybe you could have trim support without > further optimization, but that obviously isn't ideal. >
That's why I want to avoid them if at all possible. The best way to know what I'm getting is to get what I know works best due to the fact they been around for ages. To your point tho, it would likely take quite some effort to make every layer aware of SMR. Like you said, everything has to detect it and be able to work with it or it fails and defaults to what we know slows things down, to a crawl in some large write situations. I read some of the link that was posted. I'm going to try to read it again and hopefully finish it later, after I dig up and replace about a 100 feet of sewer line. Tractor and really, REALLY, wet soil does not go well for a sewer line only a few inches underground. Gonna have to go deeper and put some better fill in this time. Dale :-) :-)
