Re: [PATCH][TAKE-1] fs/btrfs: Return EPERM for rmdir on subvolumes and snapshots

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/09/2010 11:54 AM, Goffredo Baroncelli wrote:
        EBUSY (not on Linux)
               The file pathname cannot be unlinked because it is being used by
               the system or another process and the  implementation  considers
               this an error.

[...]
        EPERM  The system does not allow unlinking of directories, or unlinking
               of directories requires  privileges  that  the  calling  process
               doesn't  have.   (This  is the POSIX prescribed error return; as
               noted above, Linux returns EISDIR for this case.)

        EPERM (Linux only)
               The file system does not allow unlinking of files.

[...]

In fact when I tried to unlink a directory where a filesystem is mounted, I
got -EBUSY. So for consistency EBUSY may be another error which may be
returned.

EBUSY is again meant for different reason where in a super block is being locked or accessed by an Application which would mean unref on that block would cause Application to go nuts. In such cases EBUSY is returned.


--

Harshavardhana
http://www.gluster.com

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux