[lkml]   [2011]   [Jun]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: unlink(nonexistent): EROFS or ENOENT?
    On Sun, May 29, 2011 at 08:08:55PM +0400, Michael Tokarev wrote:
    > Hello.
    > Just noticed that at least on ext4, unlinking a
    > non-existing file from a read-only filesystem
    > results in EROFS instead of ENOENT. I'd expect
    > it return ENOENT - it is more logical, at least
    > in my opinion.
    > For one, (readonly) NFS mount returns ENOENT in
    > this case.

    Um, it doesn't for me. Testing on v3.0-rc1:

    # ls /test/foo; rm /test/foo
    ls: cannot access /test/foo: No such file or directory
    rm: cannot remove `/test/foo': No such file or directory
    # ls /test/null; rm /test/null
    rm: cannot remove `/test/null': Read-only file system
    # grep test /proc/mounts
    /dev/vdb /test ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0

    - Ted

     \ /
      Last update: 2011-06-06 05:43    [W:0.042 / U:24.348 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site