{"id":24912,"date":"2017-02-05T03:01:35","date_gmt":"2017-02-04T17:01:35","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=24912"},"modified":"2017-02-10T21:54:31","modified_gmt":"2017-02-10T11:54:31","slug":"linux-inode-file-removal-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/linux-inode-file-removal-tutorial\/","title":{"rendered":"Linux Inode File Removal Tutorial"},"content":{"rendered":"
\"Linux<\/a>

Linux Inode File Removal Tutorial<\/p><\/div>\n

We think of the Linux and Unix concept of an “inode”<\/a> as interesting in terms of an organizational design for a hard disk operating system, but more of a curiosity in most day to day interfacing to Linux. After all, Windows and DOS don’t use, or seem to need the concept. You may want to read more about this at Linux Inode Primer Tutorial<\/a> as shown below.<\/p>\n

That is, until, the other day, we accidentally renamed a Linux web server file to contain funny characters, somehow occurring during some FileZilla sftp operations we were doing. To FileZilla these “funny characters” only appear as a small blank left indentation to the filename as show with its GUI interface, but, go to the Linux command line via ssh and you see …<\/p>\n


\n# ls<\/a> -li
\n...
\n...
\n2596915 -rw-r--r-- 1 rjmprogr rjmprogr 44578 Sep 11 09:55 \\ \\ map.php
\n...
\n#
\n<\/code><\/p>\n

… and no matter what you try like …<\/p>\n


\n# rm<\/a> -f \"*map.php\"
\n<\/code><\/p>\n

… or …<\/p>\n


\n# mv<\/a> -i \"*map.php\" xx.xx
\n<\/code><\/p>\n

… or to attempt a clobber it with a local “map.php” via a FileZilla sftp file transfer, you cannot solve it causing problems via these conventional approaches.<\/p>\n

We knew there was a way with “inodes” but cannot embed it in the memory, for the few times you “have” to use it, so looked up Google to arrive at this very useful link<\/a>‘s advice (tip #5, starting with ls -li<\/I>), thanks, so that we ended up at the Linux command line of an ssh session, going …<\/p>\n


\nfind<\/a> . -inum 2596915 -exec rm -i {} \\;
\n<\/code><\/p>\n

… to which you get prompted about removing that rogue file from the system, allowing for an orderly FileZilla sftp file transfer of local “map.php” to be achieved. And it is at times like this that I bless the “inode” concept. Please don’t think that you can’t get into a similar problem working with Windows (or DOS), because you can, but you’ll have to discover a method not involving “inodes” to get you out of your “pickle” there.<\/p>\n

\n

Previous relevant Linux Inode Primer Tutorial<\/a> is shown below.<\/p>\n

\"Linux<\/a>

Linux Inode Primer Tutorial<\/p><\/div>\n

When you learn Unix or Linux you are taught that a lot of things about how the operating system works are about files.<\/p>\n

And with Unix and Linux those files can often be (further) referenced via a number called an inode<\/a> … to quote … <\/p>\n

\n A Unix file is “stored” in two different parts of the disk – the data blocks and the inodes. (I won’t get into superblocks and other esoteric information.) The data blocks contain the “contents” of the file. The information about the file is stored elsewhere – in the inode.\n<\/p><\/blockquote>\n

… and this inode<\/i> is examinable with the stat<\/i> command to show … (and to quote again) …<\/p>\n