Filesystems like btrfs and zfs have certain scenarios where unlink(2) can return ENOSPC. This can be rather surprising. It's usually caused by snapshots consuming all space on the underlying fs (though the docs on btrfs weren't clear and there was a lot of code to trace). Anyway, it's not covered in the unlink(2) man page and when you get an error like that it's kind of unexpected for someone with a lot of Unix experience. Kevin -- Kevin Lyda Galway, Ireland US Citizen overseas? We can vote. Register now: http://www.votefromabroad.org/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
