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 HPUX

clri

clri(1M)																  clri(1M)

NAME

       clri - clear inode

SYNOPSIS

       special i-number  ...

DESCRIPTION

       The  command  clears  the  inode i-number by filling it with zeros.  special must be a special file name referring to a device containing a
       file system.  For proper results, special should not be mounted (see WARNINGS below).  After is executed, all blocks in the  affected  file
       show up as "missing" in an of special (see fsck(1M)).  This command should only be used in emergencies.

       Read and write permission is required on the specified special device.  The inode becomes allocatable.

WARNINGS

       The  primary  purpose of this command is to remove a file that for some reason does not appear in any directory.  If it is used to clear an
       inode that does appear in a directory, care should be taken to locate the entry and remove it.  Otherwise, when the inode is reallocated to
       some  new file, the old entry in the directory will still point to that file.  At that point, removing the old entry destroys the new file,
       causing the new entry to point to an unallocated inode, so the whole cycle is likely to be repeated again.

       If the file system is mounted, is likely to be ineffective.

DEPENDENCIES

       operates only on file systems of type

SEE ALSO

       fsck(1M), fsdb(1M), ncheck(1M).

STANDARDS CONFORMANCE

       clri: SVID2, SVID3

																	  clri(1M)