On Tue, 2005-03-29 at 10:08 -0500, Cormack, Ken wrote: > What filesystem "type" are you using, that the .journal file is visible, in > the first place? > > I'm assuming you're using the EXT3 filesystem type? If so, those > filesystems, IF properly mounted with proper /etc/fstab entries, should > render the journal invisible to clam (and any other command that operates on > "files"). > > A proper EXT3-appropriate fstab entry should look like this: > > LABEL=your_label /mount_point ext3 defaults 1 2 > > If the filesystem is properly mounted as an EXT3 fs type, then doing a "ls > -al .journal" SHOULD yield a "no such file or directory" error. > > Only when an EXT3 filesystem is IMPROPERLY mounted as an EXT2 filesystem, > would the journal be visible at all.
If an ext2 fs is converted to an ext3 while it is mounted the .journal inode cannot be properly hidden. This actually goes for any mounted ext2 fs, but the ext3 driver will hide the inode on next mount. The problem comes up with the / mount point because it is mounted read only at boot, and thus is just remounted rw. So the driver has no chance to hide the inode. One way to fix this is to boot from a CD image and then mount straight out the ext3 file system under the root provided on the boot CD. -- Chris _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
