Skip to contentSkip to conversation

delete file entry and free space

DISCUSSION Anthony Chee 2 participants 4 messages May 18, 2002 – May 19, 2002 VFS

lore
Share & tools
lore
#0 lore raw

I am doing kernel module work on file system. The module holds two variable dir and dentry, and pass to myunlink function, which is below.

int myunlink(struct inode *dir, struct dentry *dentry) {

    int error = 0;

down(&dir->i_sem);
down(&dir->i_zombie);

if (dir->i_op && dir->i_op->unlink) {
if (d_mountpoint(dentry))
error = -EBUSY;
else {
lock_kernel();
error = dir->i_op->unlink(dir, dentry);
unlock_kernel();

   if (!error) {
    d_delete(dentry);

}
}
}

up(&dir->i_zombie);
if (!error)
inode_dir_notify(dir, DN_DELETE);

dput(dentry);
up(&dir->i_sem);
return error;
}

The myunlink function is a merge from sys_unlink() and vfs_unlink(), and remove some permission and quota syntax, as I need to force to delete the entry. After passing the variables to the function, the entry is disappeared while using "ls", but I found that it still occupy disk space by using command "df". How can I also free the disk space. My target is on releasing the disk space, and I don't care any permission or others. Or any other method on releasing the disk space by using dir and dentry? Thanks.

#1 lore raw
Quoted 7 lines · Anthony Chee

The myunlink function is a merge from sys_unlink() and vfs_unlink(), and remove some permission and quota syntax, as I need to force to delete the entry. After passing the variables to the function, the entry is disappeared while using "ls", but I found that it still occupy disk space by using command "df". How can I also free the disk space. My target is on releasing the disk space, and I don't care any permission or others. Or any other method on releasing the disk space by using dir and dentry? Thanks.

Unlink probably isn't enough. On unix-like systems, space is only reclaimed once there are no references to the inode. If a task has that file open, it's still got a reference. You could unlink the file and then truncate it to zero size, but any task which still has it open could write to it, causing the file to be non-zero-sized.

If you don't care about that, then see sys_ftruncate for how to proceed.

Signature · 1 line
Revolutions do not require corporate support.
#2 lore raw
Quoted 7 lines

Unlink probably isn't enough. On unix-like systems, space is only reclaimed once there are no references to the inode. If a task has that file open, it's still got a reference. You could unlink the file and then truncate it to zero size, but any task which still has it open could write to it, causing the file to be non-zero-sized.

Quoted 5 lines

If you don't care about that, then see sys_ftruncate for how to proceed.

--
Revolutions do not require corporate support.

And does "rm" also involve ftruncate process?

Quoted 1 line

From manual of unlink system call, it said the space will be resused no more

process reference to it.
How can I know any process reference to the file, and does it reflect in dentry structure? Is it dentry->d_count?

Actually, I am quite confuse on d_delete(dentry) and dput(dentry). Thanks

#3 lore raw
Quoted 1 line · Anthony Chee

And does "rm" also involve ftruncate process?

No.

Quoted 4 lines
Quoted 1 line

From manual of unlink system call, it said the space will be resused no more

process reference to it.
How can I know any process reference to the file, and does it reflect in dentry structure? Is it dentry->d_count?

it's dentry->d_inode->i_nlink. Read the code for iput(). Note that the calling chain is d_delete() -> dentry_iput() -> iput(). dentry->d_count is `how many people have a reference to this dentry', which is very different from how many people have a reference to this inode.

Quoted 1 line

Actually, I am quite confuse on d_delete(dentry) and dput(dentry). Thanks

dput is i have finished using this dentry now', d_delete is i have deleted the name this dentry refers to'.

Signature · 1 line
Revolutions do not require corporate support.