Sponsored Content
Full Discussion: Undeletable file
Operating Systems OS X (Apple) Undeletable file Post 303036990 by MadeInGermany on Friday 19th of July 2019 03:18:25 PM
Old 07-19-2019
IMHO a glob match returns even unprintable characters.
So the last proposal does not improve anything.

And the clri command (didn't know it yet), will cause extra harm.
It is useless to clear the inode of the file, because an inode contains the data block structure and all meta information BUT THE FILENAME.
The filename and the pointer to the inode is stored in the directory.
The directory is another inode. To have an effect you must clear the directory inode.
I expect less damage with
Code:
unlink <directory>

if supported by the OS. If successful, you need a full file system check, in order to collect the dangling file inode and its data blocks.
I successfully did that a couple of times on a non-journaling UFS in single-user mode (no desktop, no other processes running).

I would go for a disk editor. Find the offending name, compare the shown bytes with the characters from the ls command, change one byte, save, compare again, ...
 

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... (10 Replies)
Discussion started by: chxxangie
10 Replies

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... (9 Replies)
Discussion started by: mirrorx
9 Replies

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... (6 Replies)
Discussion started by: asnandhakumar
6 Replies

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... (10 Replies)
Discussion started by: Divya Nochiyil
10 Replies

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... (22 Replies)
Discussion started by: pottic
22 Replies
write(1)							   User Commands							  write(1)

NAME
write - write to another user SYNOPSIS
write user [terminal] DESCRIPTION
The write utility reads lines from the user's standard input and writes them to the terminal of another user. When first invoked, it writes the message: Message from sender-login-id (sending-terminal) [date]... to user. When it has successfully completed the connection, the sender's terminal will be alerted twice to indicate that what the sender is typing is being written to the recipient's terminal. If the recipient wants to reply, this can be accomplished by typing write sender-login-id [sending-terminal] upon receipt of the initial message. Whenever a line of input as delimited by a NL, EOF, or EOL special character is accumulated while in canonical input mode, the accumulated data will be written on the other user's terminal. Characters are processed as follows: o Typing the alert character will write the alert character to the recipient's terminal. o Typing the erase and kill characters will affect the sender's terminal in the manner described by the termios(3C) interface. o Typing the interrupt or end-of-file characters will cause write to write an appropriate message (EOT in the C locale) to the recipient's terminal and exit. o Typing characters from LC_CTYPE classifications print or space will cause those characters to be sent to the recipient's termi- nal. o When and only when the stty iexten local mode is enabled, additional special control characters and multi-byte or single-byte characters are processed as printable characters if their wide character equivalents are printable. o Typing other non-printable characters will cause them to be written to the recipient's terminal as follows: control characters will appear as a `^' followed by the appropriate ASCII character, and characters with the high-order bit set will appear in "meta" notation. For example, `03' is displayed as `^C' and `372' as `M-z'. To write to a user who is logged in more than once, the terminal argument can be used to indicate which terminal to write to. Otherwise, the recipient's terminal is the first writable instance of the user found in /usr/adm/utmpx, and the following informational message will be written to the sender's standard output, indicating which terminal was chosen: user is logged on more than one place. You are connected to terminal. Other locations are:terminal Permission to be a recipient of a write message can be denied or granted by use of the mesg utility. However, a user's privilege may fur- ther constrain the domain of accessibility of other users' terminals. The write utility will fail when the user lacks the appropriate priv- ileges to perform the requested action. If the character ! is found at the beginning of a line, write calls the shell to execute the rest of the line as a command. write runs setgid() (see setuid(2)) to the group ID tty, in order to have write permissions on other users' terminals. The following protocol is suggested for using write: when you first write to another user, wait for them to write back before starting to send. Each person should end a message with a distinctive signal (that is, (o) for over) so that the other person knows when to reply. The signal (oo) (for over and out) is suggested when conversation is to be terminated. OPERANDS
The following operands are supported: user User (login) name of the person to whom the message will be written. This operand must be of the form returned by the who(1) utility. terminal Terminal identification in the same format provided by the who utility. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of write: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 The addressed user is not logged on or the addressed user denies permission. FILES
/var/adm/utmpx User and accounting information for write /usr/bin/sh Bourne shell executable file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ SEE ALSO
mail(1), mesg(1), pr(1), sh(1), talk(1), who(1), setuid(2), termios(3C), attributes(5), environ(5), standards(5) DIAGNOSTICS
user is not logged on The person you are trying to write to is not logged on. Permission denied The person you are trying to write to denies that permission (with mesg). Warning: cannot respond, set mesg-y Your terminal is set to mesg n and the recipient cannot respond to you. Can no longer write to user The recipient has denied permission (mesg n) after you had started writing. SunOS 5.11 3 Nov 2000 write(1)
All times are GMT -4. The time now is 10:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy