Undeletable file Post: 303036996

Sponsored Content

Operating Systems OS X (Apple) Undeletable file Post 303036996 by hicksd8 on Saturday 20th of July 2019 05:07:36 AM

07-20-2019

Moderator

@MadeInGermany............Your synopsis of the filesystem structure is, of course, absolutely correct. The filename is in the directory inode but in my experience, if you nuke the file inode when fsck comes along it will see that the directory entry points to a now non-existant inode and ask approval to remove the file. But yes, if fsck falls over at that point because the filename is illegal or doesn't clear the file entry, then you are right that the directory inode would need to be identified and zapped in the same way too (which is possible because the file in question is the only entry in the directory). fsck can then be run again to clear up the mess. I've done this many many times when working on filesystem internals, the problem these days is that many OS's do not provide or implement clri.

I take your point that unlink directory is an easier approach if it works so let the OP try that first.

NOTE: In this case for fsck read the MacOS fsck_hfs.

Last edited by hicksd8; 07-20-2019 at 06:34 AM..

hicksd8

View Public Profile for hicksd8

Find all posts by hicksd8

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

undeletable file

when i try to ls -lrt the directory, the "undeletable" file is listed. but when i try to ls -lrt *exe, the "undeletable" file is not listed. this "undeletable" is the file that i want to delete from the directory. but when i try to delete/rename/copy.... it, it show that "No such file or...

2. UNIX for Dummies Questions & Answers

Files.... undeletable.

I've some files created by a script. For some reason last time the script run was interrupted for an error and the files produced by the script are undeletable. i've tryed as root with command 'rm' and even if i got no error in command execution the files are still there. These are the...

3. Shell Programming and Scripting

Match list of strings in File A and compare with File B, C and write to a output file in CSV format

Hi Friends, I'm a great fan of this forum... it has helped me tone my skills in shell scripting. I have a challenge here, which I'm sure you guys would help me in achieving... File A has a list of job ids and I need to compare this with the File B (*.log) and File C (extend *.log) and copy...

4. Shell Programming and Scripting

Compare 2 text file with 1 column in each file and write mismatch data to 3rd file

Hi, I need to compare 2 text files with around 60000 rows and 1 column. I need to compare these and write the mismatch data to 3rd file. File1 - file2 = file3 wc -l file1.txt 58112 wc -l file2.txt 55260 head -5 file1.txt 101214200123 101214700300 101250030067 101214100500...

5. Shell Programming and Scripting

Shell script (sh file) logic to compare contents of one file with another file and output to file

Shell script logic Hi I have 2 input files like with file 1 content as (file1) "BRGTEST-242" a.txt "BRGTEST-240" a.txt "BRGTEST-219" e.txt File 2 contents as fle(2) "BRGTEST-244" a.txt "BRGTEST-244" b.txt "BRGTEST-231" c.txt "BRGTEST-231" d.txt "BRGTEST-221" e.txt I want to get...

LEARN ABOUT OPENDARWIN

clri

CLRI(8) 						    BSD System Manager's Manual 						   CLRI(8)

NAME

     clri -- clear an inode

SYNOPSIS

     clri special_device inode_number ...

DESCRIPTION

     Clri is obsoleted for normal file system repair work by fsck(8).

     Clri zeros out the inodes with the specified inode number(s) on the filesystem residing on the given special_device.  The fsck(8) utility is
     usually run after clri to reclaim the zero'ed inode(s) and the blocks previously claimed by those inode(s).  Both read and write permission
     are required on the specified special_device.

     The primary purpose of this routine is to remove a file which for some reason is not being properly handled by fsck(8).  Once removed, it is
     anticipated that fsck(8) will be able to clean up the resulting mess.

SEE ALSO

     fsck(8), fsdb(8), icheck(8), ncheck(8)

BUGS

     If the file is open, the work of clri will be lost when the inode is written back to disk from the inode cache.

4th Berkeley Distribution					  April 19, 1994					 4th Berkeley Distribution