[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: "ext2fs_check_if_mount: No such file or directory while determining whether" messages



Theodore Tso wrote:

> This is fine, but you have to make sure that /proc is mounted
> after you remount the root read/write.  E2fsck needs to be
> able to check whether or not filesystems are mounted, and so
> that's why it's complaining about these errors:

>> ext2fs_check_if_mount: No such file or directory while determining whether /dev/ide/host0/bus0/target0/lun0/part4 is mounted.

Yes, I noticed some hours ago that /proc/mounts isn't mounted
before. Would it work if I modify my /etc/fstab and move proc
to the first line ? Actually it's:

/dev/ide/host0/bus0/target0/lun0/part1 / ext3 defaults 1 1
/dev/ide/host0/bus0/target0/lun0/part3 /usr/local/src1 ext3 defaults 1 2
/dev/ide/host0/bus0/target0/lun0/part4 /home/ftp/pub ext3 defaults 1 2
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults,size=256m 0 0
tmpfs /tmp tmpfs defaults,size=256m 0 0
tmpfs /var/lock tmpfs defaults,size=50k 0 0
tmpfs /var/run tmpfs defaults,size=100k 0 0
tmpfs /home/pervalidus/tmp tmpfs defaults,size=256m 0 0

> Can you run dumpe2fs -h on those partitions?  It looks
> like the time between checks and number of mounts between
> check has gotten reset. How or why, that's not clear, but
> you can use tune2fs -c 0 -i 0 again to avoid the
> filesystem checks from happening in the future. (It is a
> good idea to run fsck from time to time, though, just in
> case kernel bugs or hardware hiccups have introduced
> corruption in the filesystem.)

# dumpe2fs -h /dev/ide/host0/bus0/target0/lun0/part3
dumpe2fs 1.25 (20-Sep-2001)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          8c092176-9418-11d4-920a-b0cc6fece225
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal needs_recovery sparse_super
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              512512
Block count:              512071
Reserved block count:     0
Free blocks:              381590
Free inodes:              478207
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         32032
Inode blocks per group:   1001
Last mount time:          Tue Oct 16 21:28:11 2001
Last write time:          Tue Oct 16 21:28:11 2001
Mount count:              1
Maximum mount count:      20
Last checked:             Tue Oct 16 21:27:30 2001
Check interval:           15552000 (6 months)
Next check after:         Sun Apr 14 20:27:30 2002
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal UUID:             <none>
Journal inode:            8
Journal device:           0x0000
First orphan inode:       0

# dumpe2fs -h /dev/ide/host0/bus0/target0/lun0/part4
dumpe2fs 1.25 (20-Sep-2001)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          a855fb38-9418-11d4-9191-a4ef693c376b
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal needs_recovery sparse_super
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              645120
Block count:              644608
Reserved block count:     32230
Free blocks:              465479
Free inodes:              635715
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         32256
Inode blocks per group:   1008
Last mount time:          Tue Oct 16 21:28:11 2001
Last write time:          Tue Oct 16 21:28:11 2001
Mount count:              1
Maximum mount count:      20
Last checked:             Tue Oct 16 21:27:55 2001
Check interval:           15552000 (6 months)
Next check after:         Sun Apr 14 20:27:55 2002
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal UUID:             <none>
Journal inode:            8
Journal device:           0x0000
First orphan inode:       0

I'll use tune2fs again. BTW, I used it with the partitions
mounted (but not with the broken 2.4.10). Now I'm not sure if
only for -m 0 :-)

I see it's good to run fsck from time to time. For some
reason there was "Deleted inode 354821 has zero dtime.
FIXED." in part4. The partition was always cleanly unmounted.

PS: Don't reply directly to me, as I just moved to a new
service (where I forward my messages) now. The old closed
without any notice...

-- 
0 pervalidus {net, {dyndns.}org} Tel: 55-21-2717-2399 (Niterói-RJ BR)





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]