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

df report



'df' doesn't report my root partition, but does report my
/boot partition when both are mounted with <type> auto. But
when mounted with <type> ext3, both partitions are reported.

Details:

The system has mount-2.11m, tune2fs-1.25 and df (fileutils) 4.1

I just created an ext3 fs on a new Debian Woody install initially
running linux-2.2.19 on ext2, but upgraded to linux-2.4.15-pre6
and then ran:
'tune2fs -j /dev/hda[1,3]'

and then editing fstab to
---
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>                       
<dump> <pass>
/dev/hda3       /               auto    defaults,errors=remount-ro      0   
   1
/dev/hda2       none            swap    sw                      0       0
proc            /proc           proc    defaults                        0   
   0
/dev/fd0        /floppy         auto    defaults,user,noauto            0   
   0
/dev/cdrom      /cdrom          iso9660 defaults,ro,user,noauto         0   
   0
/dev/hda1       /boot   auto    defaults                        0       2
---

but upon reboot, 'df -h' shows:
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1              61M  5.0M   52M   9% /boot


so I changed the <type> to "ext3" in fstab, rebooted and now 'df -h'
shows:
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda3             9.0G  169M  8.3G   2% /
/dev/hda1              61M  5.0M   52M   9% /boot

as expected.


Running 'mount' on the <type> "auto" mounted system gives:
/dev/hda3 on / type auto (rw,errors=remount-ro,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda1 on /boot type ext3 (rw)


while running 'mount' on "ext3" mounted gives:
/dev/hda3 on / type ext3 (rw,errors=remount-ro,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda1 on /boot type ext3 (rw)


running 'tune2fs -l /dev/hda3' gives:
---
tune2fs 1.25 (20-Sep-2001)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          b1ceff3e-caca-4635-b6aa-3712b63f8917
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal filetype needs_recovery sparse_super
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              1198208
Block count:              2395693
Reserved block count:     119784
Free blocks:              2315027
Free inodes:              1183124
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16192
Inode blocks per group:   506
Last mount time:          Sun Nov 18 14:21:10 2001
Last write time:          Sun Nov 18 14:21:10 2001
Mount count:              5
Maximum mount count:      10
Last checked:             Sun Nov 18 14:10:39 2001
Check interval:           15552000 (6 months)
Next check after:         Fri May 17 15:10:39 2002
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal UUID:             <none>
Journal inode:            12
Journal device:           0x0000
First orphan inode:       0
---

and 'tune2fs -l /dev/hda1' gives:
---
tune2fs 1.25 (20-Sep-2001)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          416e51d1-8342-49bf-8725-bd468cd1c804
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal filetype needs_recovery sparse_super
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              16064
Block count:              64228
Reserved block count:     3211
Free blocks:              57077
Free inodes:              16040
First block:              1
Block size:               1024
Fragment size:            1024
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2008
Inode blocks per group:   251
Last mount time:          Sun Nov 18 22:23:30 2001
Last write time:          Sun Nov 18 22:23:30 2001
Mount count:              6
Maximum mount count:      10
Last checked:             Sun Nov 18 22:11:09 2001
Check interval:           15552000 (6 months)
Next check after:         Fri May 17 23:11:09 2002
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal UUID:             <none>
Journal inode:            12
Journal device:           0x0000
First orphan inode:       0
---

Is this a 'df' bug or an ext3 bug?


Thanks,
Jeremiah





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