Hi,
Thank you all.
Looks like I forgot to run "mkfs.ext3 /dev/sdb1" after I used
"fdisk /dev/sdb" to partitioned it. originally this disk has many linux
partitions, after I repartitioned it to a single one, then reboot, it
automatically mounted as 9.2G disk. then I copied some 5.3G data onto
it.
The following is what I have just done, seems ok now.(although claimed
160G disk only has 140G can be use , too bad :) )
---------------------------------------------
[root@pc1 media]# umount /media/disk
[root@pc1 media]# df
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda7 ext3 38G 23G 14G 63% /
tmpfs tmpfs 474M 12K 474M 1% /dev/shm
/dev/sda9 ext3 66G 61G 1.3G 98% /home
/dev/sda1 vfat 15G 8.4G 6.4G 57% /media/disk-1
/dev/sda5 vfat 25G 18G 7.1G 72% /media/disk-2
/dev/sda6 ext3 38G 3.9G 33G 11% /media/_home
[root@pc1 media]# e2fsck -n /dev/sdb1
e2fsck 1.40.2 (12-Jul-2007)
/dev/sdb1: clean, 56/1224000 files, 2126723/2443880 blocks
[root@pc1 media]# mkfs.ext3 /dev/sdb1
mke2fs 1.40.2 (12-Jul-2007)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
19546112 inodes, 39072080 blocks
1953604 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
1193 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root@pc1 media]# mount /dev/sdb1 /media/disk
mount: mount point /media/disk does not exist
[root@pc1 media]# mount /dev/sdb1 /mnt/tmp
[root@pc1 media]# df
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda7 ext3 38G 23G 14G 63% /
tmpfs tmpfs 474M 12K 474M 1% /dev/shm
/dev/sda9 ext3 66G 61G 1.3G 98% /home
/dev/sda1 vfat 15G 8.4G 6.4G 57% /media/disk-1
/dev/sda5 vfat 25G 18G 7.1G 72% /media/disk-2
/dev/sda6 ext3 38G 3.9G 33G 11% /media/_home
/dev/sdb1 ext3 147G 188M 140G 1% /mnt/tmp
[root@pc1 media]#
--------------------------------------------
On Sun, 2007-12-09 at 14:16 +0900, John Summerfield wrote:
> Mikkel L. Ellertson wrote:
>
> >>
> >> Then you mount it (e.g. man fstab &/or man mount).
> >>
> > It looks like the drive is already one big partition with an ext3
> > file system on it, but it is only shown as being 9.2G. It almost
> > looks like the partition was resized but the file system wasn't. If
> > it didn't already have 5.3G of data on it, it would be tempting to
> > delete and recreate the file system.
> >
> > Mikkel
> >
>
> Mikkel looks closest so far to me.
>
> Unmount the partition.
> run e2fsck:
> e2fsck -n /dev/sdb1
>
> That's a read-only test.
>
> If that looks okay, then
> man resize2fs
> resize2fs <whatever seems good> /dev/sdb1
>
> if that wants you you to e2fsck with more options, do it, then try again.
>
> Mount the partition again, then
> \df -h /media/disk-1
> and see whether it looks better.
>
>
> I can only guess at how you got that partition's data that way.
> a. Copy a drive over like so:
> dd if=/dev/diskb of=/dev/diskc
> but that doesn't explain the partition's size.
> b. Partition to one big partition, then copy some data thus:
> dd if=/dev/diskb1 of=/dev/diskc1
> which could leave a filesystem that doesn't fill the partition.
>
>
>
>
>
>
>
> --
>
> Cheers
> John
>
> -- spambait
> 1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx
> -- Advice
> http://webfoot.com/advice/email.top.php
> http://www.catb.org/~esr/faqs/smart-questions.html
> http://support.microsoft.com/kb/555375
>
> You cannot reply off-list:-)
>
