How to delete a file with corrupt filename?
Clash Royale CLAN TAG#URR8PPP
up vote
5
down vote
favorite
Somehow a program created a file with a broken filename which cannot be deleted anymore. Any attempt to delete the file results in "No such file or directory" as if the file isn't there.
The problem seems to be a control character ASCII 2 in the filename.
$ ls
??[????é?X
$ ls | xxd
00000000: 3f3f 5b3f 3f02 3f3f d8a9 3f58 0a ??[??.??..?X.
# Typing '?' and letting the bash complete the filename
$ rm ??[??^B??é?X
rm: das Entfernen von '??[??'$'02''??é?X' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
$ rm *
rm: das Entfernen von '??[??'$'02''??é?X' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
$ ls -i
2532 ??[?????é?X
$ find -inum 2532 -delete
find: âÂÂ./??[??02??é?Xâ kann nicht gelöscht werden.: Datei oder Verzeichnis nicht gefunden
I tried to run fsck
after reboot but the file is still there.
$ zcat /var/log/upstart/mountall.log.1.gz
...
fsck von util-linux 2.25.1
/dev/sdc3: sauber, 544937/6815744 Dateien, 21618552/27242752 Blöcke
...
No indication there was a problem. ("sauber" = clean)
I even tried to wrote my own deletion program which failed as well as the rm
command:
$ cat fix.c
#include <stdio.h>
#include <errno.h>
int main()
char filename[20];
sprintf(filename, "%c%c%c%c%c%c%c%c%c%c%c%c", 0x3f,0x3f,0x5b,0x3f,0x3f,0x02,0x3f,0x3f,0xd8,0xa9,0x3f,0x58);
printf("filename = %sn", filename);
int result = remove(filename);
printf("result = %dn", result);
printf("errno = %dn", errno);
perror("Error");
return 0;
$ gcc -o fix fix.c && ./fix
filename = ??[????é?X
result = -1
errno = 2
Error: No such file or directory
I found similar questions the answers there don't work for me:
- https://serverfault.com/questions/565914/remove-corrupt-file-with-bad-file-name-linux
- How to delete this undeletable directory?
Other information:
$ mount | grep " / "
/dev/sdc3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
$ uname -a
Linux hera 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/issue
Ubuntu 17.10 n l
Is there a way to get rid of this file?
files delete
add a comment |Â
up vote
5
down vote
favorite
Somehow a program created a file with a broken filename which cannot be deleted anymore. Any attempt to delete the file results in "No such file or directory" as if the file isn't there.
The problem seems to be a control character ASCII 2 in the filename.
$ ls
??[????é?X
$ ls | xxd
00000000: 3f3f 5b3f 3f02 3f3f d8a9 3f58 0a ??[??.??..?X.
# Typing '?' and letting the bash complete the filename
$ rm ??[??^B??é?X
rm: das Entfernen von '??[??'$'02''??é?X' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
$ rm *
rm: das Entfernen von '??[??'$'02''??é?X' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
$ ls -i
2532 ??[?????é?X
$ find -inum 2532 -delete
find: âÂÂ./??[??02??é?Xâ kann nicht gelöscht werden.: Datei oder Verzeichnis nicht gefunden
I tried to run fsck
after reboot but the file is still there.
$ zcat /var/log/upstart/mountall.log.1.gz
...
fsck von util-linux 2.25.1
/dev/sdc3: sauber, 544937/6815744 Dateien, 21618552/27242752 Blöcke
...
No indication there was a problem. ("sauber" = clean)
I even tried to wrote my own deletion program which failed as well as the rm
command:
$ cat fix.c
#include <stdio.h>
#include <errno.h>
int main()
char filename[20];
sprintf(filename, "%c%c%c%c%c%c%c%c%c%c%c%c", 0x3f,0x3f,0x5b,0x3f,0x3f,0x02,0x3f,0x3f,0xd8,0xa9,0x3f,0x58);
printf("filename = %sn", filename);
int result = remove(filename);
printf("result = %dn", result);
printf("errno = %dn", errno);
perror("Error");
return 0;
$ gcc -o fix fix.c && ./fix
filename = ??[????é?X
result = -1
errno = 2
Error: No such file or directory
I found similar questions the answers there don't work for me:
- https://serverfault.com/questions/565914/remove-corrupt-file-with-bad-file-name-linux
- How to delete this undeletable directory?
Other information:
$ mount | grep " / "
/dev/sdc3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
$ uname -a
Linux hera 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/issue
Ubuntu 17.10 n l
Is there a way to get rid of this file?
files delete
First, usels -b
to find out what it's really called.
â Ignacio Vazquez-Abrams
Nov 4 '17 at 22:21
Why wouldrm *
be a good idea? :p
â Jesse_b
Nov 4 '17 at 22:23
fsck.ext4 -f
, and if that does not help, try your luck withdebugfs
â frostschutz
Nov 4 '17 at 22:29
@Jesse_b plan was: when you cannot name the file, tellrm
to just delete everything. The folder was otherwise empty, because you can move other files out of there.
â theHacker
Nov 5 '17 at 10:08
add a comment |Â
up vote
5
down vote
favorite
up vote
5
down vote
favorite
Somehow a program created a file with a broken filename which cannot be deleted anymore. Any attempt to delete the file results in "No such file or directory" as if the file isn't there.
The problem seems to be a control character ASCII 2 in the filename.
$ ls
??[????é?X
$ ls | xxd
00000000: 3f3f 5b3f 3f02 3f3f d8a9 3f58 0a ??[??.??..?X.
# Typing '?' and letting the bash complete the filename
$ rm ??[??^B??é?X
rm: das Entfernen von '??[??'$'02''??é?X' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
$ rm *
rm: das Entfernen von '??[??'$'02''??é?X' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
$ ls -i
2532 ??[?????é?X
$ find -inum 2532 -delete
find: âÂÂ./??[??02??é?Xâ kann nicht gelöscht werden.: Datei oder Verzeichnis nicht gefunden
I tried to run fsck
after reboot but the file is still there.
$ zcat /var/log/upstart/mountall.log.1.gz
...
fsck von util-linux 2.25.1
/dev/sdc3: sauber, 544937/6815744 Dateien, 21618552/27242752 Blöcke
...
No indication there was a problem. ("sauber" = clean)
I even tried to wrote my own deletion program which failed as well as the rm
command:
$ cat fix.c
#include <stdio.h>
#include <errno.h>
int main()
char filename[20];
sprintf(filename, "%c%c%c%c%c%c%c%c%c%c%c%c", 0x3f,0x3f,0x5b,0x3f,0x3f,0x02,0x3f,0x3f,0xd8,0xa9,0x3f,0x58);
printf("filename = %sn", filename);
int result = remove(filename);
printf("result = %dn", result);
printf("errno = %dn", errno);
perror("Error");
return 0;
$ gcc -o fix fix.c && ./fix
filename = ??[????é?X
result = -1
errno = 2
Error: No such file or directory
I found similar questions the answers there don't work for me:
- https://serverfault.com/questions/565914/remove-corrupt-file-with-bad-file-name-linux
- How to delete this undeletable directory?
Other information:
$ mount | grep " / "
/dev/sdc3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
$ uname -a
Linux hera 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/issue
Ubuntu 17.10 n l
Is there a way to get rid of this file?
files delete
Somehow a program created a file with a broken filename which cannot be deleted anymore. Any attempt to delete the file results in "No such file or directory" as if the file isn't there.
The problem seems to be a control character ASCII 2 in the filename.
$ ls
??[????é?X
$ ls | xxd
00000000: 3f3f 5b3f 3f02 3f3f d8a9 3f58 0a ??[??.??..?X.
# Typing '?' and letting the bash complete the filename
$ rm ??[??^B??é?X
rm: das Entfernen von '??[??'$'02''??é?X' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
$ rm *
rm: das Entfernen von '??[??'$'02''??é?X' ist nicht möglich: Datei oder Verzeichnis nicht gefunden
$ ls -i
2532 ??[?????é?X
$ find -inum 2532 -delete
find: âÂÂ./??[??02??é?Xâ kann nicht gelöscht werden.: Datei oder Verzeichnis nicht gefunden
I tried to run fsck
after reboot but the file is still there.
$ zcat /var/log/upstart/mountall.log.1.gz
...
fsck von util-linux 2.25.1
/dev/sdc3: sauber, 544937/6815744 Dateien, 21618552/27242752 Blöcke
...
No indication there was a problem. ("sauber" = clean)
I even tried to wrote my own deletion program which failed as well as the rm
command:
$ cat fix.c
#include <stdio.h>
#include <errno.h>
int main()
char filename[20];
sprintf(filename, "%c%c%c%c%c%c%c%c%c%c%c%c", 0x3f,0x3f,0x5b,0x3f,0x3f,0x02,0x3f,0x3f,0xd8,0xa9,0x3f,0x58);
printf("filename = %sn", filename);
int result = remove(filename);
printf("result = %dn", result);
printf("errno = %dn", errno);
perror("Error");
return 0;
$ gcc -o fix fix.c && ./fix
filename = ??[????é?X
result = -1
errno = 2
Error: No such file or directory
I found similar questions the answers there don't work for me:
- https://serverfault.com/questions/565914/remove-corrupt-file-with-bad-file-name-linux
- How to delete this undeletable directory?
Other information:
$ mount | grep " / "
/dev/sdc3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
$ uname -a
Linux hera 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/issue
Ubuntu 17.10 n l
Is there a way to get rid of this file?
files delete
asked Nov 4 '17 at 22:19
theHacker
1464
1464
First, usels -b
to find out what it's really called.
â Ignacio Vazquez-Abrams
Nov 4 '17 at 22:21
Why wouldrm *
be a good idea? :p
â Jesse_b
Nov 4 '17 at 22:23
fsck.ext4 -f
, and if that does not help, try your luck withdebugfs
â frostschutz
Nov 4 '17 at 22:29
@Jesse_b plan was: when you cannot name the file, tellrm
to just delete everything. The folder was otherwise empty, because you can move other files out of there.
â theHacker
Nov 5 '17 at 10:08
add a comment |Â
First, usels -b
to find out what it's really called.
â Ignacio Vazquez-Abrams
Nov 4 '17 at 22:21
Why wouldrm *
be a good idea? :p
â Jesse_b
Nov 4 '17 at 22:23
fsck.ext4 -f
, and if that does not help, try your luck withdebugfs
â frostschutz
Nov 4 '17 at 22:29
@Jesse_b plan was: when you cannot name the file, tellrm
to just delete everything. The folder was otherwise empty, because you can move other files out of there.
â theHacker
Nov 5 '17 at 10:08
First, use
ls -b
to find out what it's really called.â Ignacio Vazquez-Abrams
Nov 4 '17 at 22:21
First, use
ls -b
to find out what it's really called.â Ignacio Vazquez-Abrams
Nov 4 '17 at 22:21
Why would
rm *
be a good idea? :pâ Jesse_b
Nov 4 '17 at 22:23
Why would
rm *
be a good idea? :pâ Jesse_b
Nov 4 '17 at 22:23
fsck.ext4 -f
, and if that does not help, try your luck with debugfs
â frostschutz
Nov 4 '17 at 22:29
fsck.ext4 -f
, and if that does not help, try your luck with debugfs
â frostschutz
Nov 4 '17 at 22:29
@Jesse_b plan was: when you cannot name the file, tell
rm
to just delete everything. The folder was otherwise empty, because you can move other files out of there.â theHacker
Nov 5 '17 at 10:08
@Jesse_b plan was: when you cannot name the file, tell
rm
to just delete everything. The folder was otherwise empty, because you can move other files out of there.â theHacker
Nov 5 '17 at 10:08
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
There are a bunch of options for deleting files with non-ascii filenames.
I was able to create and delete a file with the filename under discussion by using ANSI C quoting:
# Create the offending file
touch $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
# Verify that the file was created
ls -lib
# Remove the offending file
rm $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
Take a look at this post:
- identify files with non-ASCII or non-printable characters in file name
Here's a command taken from that post that should delete all files in the current directory whose names contain non-ascii characters:
LC_ALL=C find . -maxdepth 0 -name '*[! -~]*' -delete
You can modify the glob pattern or use a regular expression in order to narrow down the matches.
Here's another relevant post:
- How to delete a file with a weird name?
There's a suggestion there to try deleting by inode. First run ls -lib
to find the inode of the offending file, and then run the following command to delete it:
find . -maxdepth 1 -inum $INODE_NUM -delete
You might also find the following article to be generally useful:
- Fixing Unix/Linux/POSIX Filenames: Control Characters (such as Newline), Leading Dashes, and Other Problems
add a comment |Â
up vote
2
down vote
accepted
Always double check on which partition your files are ;-)
Turns out the bad file was not on my root partition but on a cifs
mount.
To get rid of the file the solution was just like there:
Delete the file on the target maschine. There the rm
command works normally.
I think you're supposed to accept this solution if it solved your problem. Otherwise this question will remain open.
â igal
Nov 5 '17 at 19:30
@igal: thx for the reminder. Accepting your own answer was not possible directly after writing it. There was an error message telling you had to wait a few days.
â theHacker
Nov 7 '17 at 21:53
Yeah, sorry about that. I forgot about the delay. Anyway, glad you got it sorted out.
â igal
Nov 7 '17 at 21:56
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
There are a bunch of options for deleting files with non-ascii filenames.
I was able to create and delete a file with the filename under discussion by using ANSI C quoting:
# Create the offending file
touch $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
# Verify that the file was created
ls -lib
# Remove the offending file
rm $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
Take a look at this post:
- identify files with non-ASCII or non-printable characters in file name
Here's a command taken from that post that should delete all files in the current directory whose names contain non-ascii characters:
LC_ALL=C find . -maxdepth 0 -name '*[! -~]*' -delete
You can modify the glob pattern or use a regular expression in order to narrow down the matches.
Here's another relevant post:
- How to delete a file with a weird name?
There's a suggestion there to try deleting by inode. First run ls -lib
to find the inode of the offending file, and then run the following command to delete it:
find . -maxdepth 1 -inum $INODE_NUM -delete
You might also find the following article to be generally useful:
- Fixing Unix/Linux/POSIX Filenames: Control Characters (such as Newline), Leading Dashes, and Other Problems
add a comment |Â
up vote
3
down vote
There are a bunch of options for deleting files with non-ascii filenames.
I was able to create and delete a file with the filename under discussion by using ANSI C quoting:
# Create the offending file
touch $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
# Verify that the file was created
ls -lib
# Remove the offending file
rm $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
Take a look at this post:
- identify files with non-ASCII or non-printable characters in file name
Here's a command taken from that post that should delete all files in the current directory whose names contain non-ascii characters:
LC_ALL=C find . -maxdepth 0 -name '*[! -~]*' -delete
You can modify the glob pattern or use a regular expression in order to narrow down the matches.
Here's another relevant post:
- How to delete a file with a weird name?
There's a suggestion there to try deleting by inode. First run ls -lib
to find the inode of the offending file, and then run the following command to delete it:
find . -maxdepth 1 -inum $INODE_NUM -delete
You might also find the following article to be generally useful:
- Fixing Unix/Linux/POSIX Filenames: Control Characters (such as Newline), Leading Dashes, and Other Problems
add a comment |Â
up vote
3
down vote
up vote
3
down vote
There are a bunch of options for deleting files with non-ascii filenames.
I was able to create and delete a file with the filename under discussion by using ANSI C quoting:
# Create the offending file
touch $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
# Verify that the file was created
ls -lib
# Remove the offending file
rm $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
Take a look at this post:
- identify files with non-ASCII or non-printable characters in file name
Here's a command taken from that post that should delete all files in the current directory whose names contain non-ascii characters:
LC_ALL=C find . -maxdepth 0 -name '*[! -~]*' -delete
You can modify the glob pattern or use a regular expression in order to narrow down the matches.
Here's another relevant post:
- How to delete a file with a weird name?
There's a suggestion there to try deleting by inode. First run ls -lib
to find the inode of the offending file, and then run the following command to delete it:
find . -maxdepth 1 -inum $INODE_NUM -delete
You might also find the following article to be generally useful:
- Fixing Unix/Linux/POSIX Filenames: Control Characters (such as Newline), Leading Dashes, and Other Problems
There are a bunch of options for deleting files with non-ascii filenames.
I was able to create and delete a file with the filename under discussion by using ANSI C quoting:
# Create the offending file
touch $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
# Verify that the file was created
ls -lib
# Remove the offending file
rm $'x3fx3fx5bx3fx3fx02x3fx3fxd8xa9x3fx58x0a'
Take a look at this post:
- identify files with non-ASCII or non-printable characters in file name
Here's a command taken from that post that should delete all files in the current directory whose names contain non-ascii characters:
LC_ALL=C find . -maxdepth 0 -name '*[! -~]*' -delete
You can modify the glob pattern or use a regular expression in order to narrow down the matches.
Here's another relevant post:
- How to delete a file with a weird name?
There's a suggestion there to try deleting by inode. First run ls -lib
to find the inode of the offending file, and then run the following command to delete it:
find . -maxdepth 1 -inum $INODE_NUM -delete
You might also find the following article to be generally useful:
- Fixing Unix/Linux/POSIX Filenames: Control Characters (such as Newline), Leading Dashes, and Other Problems
edited Nov 5 '17 at 6:07
answered Nov 4 '17 at 22:57
igal
4,830930
4,830930
add a comment |Â
add a comment |Â
up vote
2
down vote
accepted
Always double check on which partition your files are ;-)
Turns out the bad file was not on my root partition but on a cifs
mount.
To get rid of the file the solution was just like there:
Delete the file on the target maschine. There the rm
command works normally.
I think you're supposed to accept this solution if it solved your problem. Otherwise this question will remain open.
â igal
Nov 5 '17 at 19:30
@igal: thx for the reminder. Accepting your own answer was not possible directly after writing it. There was an error message telling you had to wait a few days.
â theHacker
Nov 7 '17 at 21:53
Yeah, sorry about that. I forgot about the delay. Anyway, glad you got it sorted out.
â igal
Nov 7 '17 at 21:56
add a comment |Â
up vote
2
down vote
accepted
Always double check on which partition your files are ;-)
Turns out the bad file was not on my root partition but on a cifs
mount.
To get rid of the file the solution was just like there:
Delete the file on the target maschine. There the rm
command works normally.
I think you're supposed to accept this solution if it solved your problem. Otherwise this question will remain open.
â igal
Nov 5 '17 at 19:30
@igal: thx for the reminder. Accepting your own answer was not possible directly after writing it. There was an error message telling you had to wait a few days.
â theHacker
Nov 7 '17 at 21:53
Yeah, sorry about that. I forgot about the delay. Anyway, glad you got it sorted out.
â igal
Nov 7 '17 at 21:56
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Always double check on which partition your files are ;-)
Turns out the bad file was not on my root partition but on a cifs
mount.
To get rid of the file the solution was just like there:
Delete the file on the target maschine. There the rm
command works normally.
Always double check on which partition your files are ;-)
Turns out the bad file was not on my root partition but on a cifs
mount.
To get rid of the file the solution was just like there:
Delete the file on the target maschine. There the rm
command works normally.
answered Nov 5 '17 at 10:06
theHacker
1464
1464
I think you're supposed to accept this solution if it solved your problem. Otherwise this question will remain open.
â igal
Nov 5 '17 at 19:30
@igal: thx for the reminder. Accepting your own answer was not possible directly after writing it. There was an error message telling you had to wait a few days.
â theHacker
Nov 7 '17 at 21:53
Yeah, sorry about that. I forgot about the delay. Anyway, glad you got it sorted out.
â igal
Nov 7 '17 at 21:56
add a comment |Â
I think you're supposed to accept this solution if it solved your problem. Otherwise this question will remain open.
â igal
Nov 5 '17 at 19:30
@igal: thx for the reminder. Accepting your own answer was not possible directly after writing it. There was an error message telling you had to wait a few days.
â theHacker
Nov 7 '17 at 21:53
Yeah, sorry about that. I forgot about the delay. Anyway, glad you got it sorted out.
â igal
Nov 7 '17 at 21:56
I think you're supposed to accept this solution if it solved your problem. Otherwise this question will remain open.
â igal
Nov 5 '17 at 19:30
I think you're supposed to accept this solution if it solved your problem. Otherwise this question will remain open.
â igal
Nov 5 '17 at 19:30
@igal: thx for the reminder. Accepting your own answer was not possible directly after writing it. There was an error message telling you had to wait a few days.
â theHacker
Nov 7 '17 at 21:53
@igal: thx for the reminder. Accepting your own answer was not possible directly after writing it. There was an error message telling you had to wait a few days.
â theHacker
Nov 7 '17 at 21:53
Yeah, sorry about that. I forgot about the delay. Anyway, glad you got it sorted out.
â igal
Nov 7 '17 at 21:56
Yeah, sorry about that. I forgot about the delay. Anyway, glad you got it sorted out.
â igal
Nov 7 '17 at 21:56
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f402558%2fhow-to-delete-a-file-with-corrupt-filename%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
First, use
ls -b
to find out what it's really called.â Ignacio Vazquez-Abrams
Nov 4 '17 at 22:21
Why would
rm *
be a good idea? :pâ Jesse_b
Nov 4 '17 at 22:23
fsck.ext4 -f
, and if that does not help, try your luck withdebugfs
â frostschutz
Nov 4 '17 at 22:29
@Jesse_b plan was: when you cannot name the file, tell
rm
to just delete everything. The folder was otherwise empty, because you can move other files out of there.â theHacker
Nov 5 '17 at 10:08