> This is expected behavior, isn't?

I would prefer that the test skips itself when the disk is full: on "OSError: [Errno 28] No space left on device".

Or maybe largefile resource should be excluded from "all"... at least on Windows, since NTFS doesn't see to support files full of zeros without accounting zero bytes (seek + write 1 byte: NTFS counts the seek in the disk space).