My testing indicates this is fixed when using the linux kernel 3.3 image. Can anyone confirm that it's not an e2fsprogs issue?
My testing indicates this is fixed when using the linux kernel 3.3 image. Can anyone confirm that it's not an e2fsprogs issue?