On 2020-07-24 at 09:22, tomas@tuxteam.de wrote: > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote: > >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote: >> >>> Sounds like a case where directly editing the underlying device, >>> to modify inode-or-equivalent contents such that the slash is no >>> longer > ^^^^^ > Nitpick: the directory entry is the one carrying the name. I had the impression that even a directory is stored in/as something that is at least analogous to an inode. Is there a different term that's more appropriate for the on-disk structure which holds a directory, vs. 'inode' for the one that holds a file? >>> there, might even be *advisable*. >> >> Yeah, some sort of direct hex-edit on the unmounted file system's >> device might be the only way to rename the file. > > If you have ext<n> (for n>=2), you're lucky (actually, aren't we > all, with so many high-quality file systems to choose from?). > > The file system check utility seems to take care of it (at least, > the source code [1] suggests that). > [1] https://sources.debian.org/src/e2fsprogs/1.45.6-1/e2fsck/pass2.c/?hl=494:503#L494 It does seem to suggest that, but when I run $ /sbin/e2fsck /tmp/testfs on the tiny filesystem created as in my previous mail, it doesn't report finding any problems and seem to change anything. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature