> > Hi all, > > any suggestion regarding the issue? > > > > Regards. > > > > Unfortunately, there isn't much a filesystem can do here. I'll need to talk with > device-mapper folks to get a better understanding how we can handle such cases, > if possible at all. > > The problem you are seeing there is because of buffered writes, you don't get a > ENOSPC because the device itself virtually still has space to be allocated, so > the lack of space is only visible when the blocks are really being allocated > from the POOL itself, but still, there isn't much a filesystem can do here > regarding buffered writes. > > As you noticed, XFS will report errors regarding the problems to write metadata > to the device, but again, user data, is up to the application to ensure the data > is consistent, although >I think I actually found a problem with it while doing > some tests as you mentioned, I'll need to look deeper into them. Disregard this comment, I messed up with some tests, so, basically, the application is responsible for the user data, and need to use fsync/fdatasync to ensure the data is properly written, this is not FS responsibility. cheers > > > -- > Carlos > -- > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Carlos -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
