7:14 p.m.
hello:
I recently added additional 160GB disk to my F8 system. and partitioned
it as a single partition.
but when I use "df" command to show my disk, it only show the size is
9.2G
on my Desktop. GNOME it can show the disk as 149.0Gb correctly.
how to fix this problem?
the following is my disk info.
---------------------------------------------------------------------
[root@pc1 ~]# df
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda7 ext3 38G 15G 22G 41% /
tmpfs tmpfs 474M 12K 474M 1% /dev/shm
/dev/sda9 ext3 66G 61G 1.3G 98% /home
/dev/sda5 vfat 25G 18G 7.1G 72% /media/disk
/dev/sdb1 ext3 9.2G 5.3G 3.5G 61% /media/disk-1
/dev/sda1 vfat 15G 8.3G 6.4G 57% /media/disk-2
/dev/sda6 ext3 38G 3.9G 33G 11% /media/_home
[root@pc1 ~]# fdisk /dev/sdb
The number of cylinders for this disk is set to 19457.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe2c5e2d5
Device Boot Start End Blocks Id System
/dev/sdb1 1 19457 156288321 83 Linux
Command (m for help): q
[root@pc1 ~]#
------------------------------------------------------------------
thanks,
zhu
10:18 a.m.
zhu blue wrote:
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.
In the future, you may find that parted works better for doing this.
It will even let you format the partition in the same program.
The following is what I have just done, seems ok now.(although
claimed
160G disk only has 140G can be use , too bad :) )
Unless you specify otherwise when you create the file system, 5% is
reserved for root. You also lose disk space because of file system
overhead. Then you have the fact that hard drive size is usually
given with k=1000 - it looks better when advertising drive size.
Mikkel
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting a bad thing?
11:09 p.m.
On Sat, 2007-12-08 at 22:00 -0600, Mikkel L. Ellertson wrote:
The partition is approx 160 GB, but from the output of df, the file
system is only 9.2 GB. So the file system is only a fraction of the
size of the partition. Unless there is a bug in df so that it is
mis-reporting the size of the file system, then the file system does
not fill the partition.
The original poster needs to step in here. But I'd be guessing that
they used dd to copy something over.
On F7, at least, df certainly works correctly with drives well above
160GB. For me, at least...
--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
8:51 p.m.
On Sun, 2007-12-09 at 09:14 +0800, zhu blue wrote:
I recently added additional 160GB disk to my F8 system. and
partitioned
it as a single partition. but when I use "df" command to show my
disk, it only show the size is 9.2G on my Desktop. GNOME it can show
the disk as 149.0Gb correctly.
[root@pc1 ~]# df
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda7 ext3 38G 15G 22G 41% /
tmpfs tmpfs 474M 12K 474M 1% /dev/shm
/dev/sda9 ext3 66G 61G 1.3G 98% /home
/dev/sda5 vfat 25G 18G 7.1G 72% /media/disk
/dev/sdb1 ext3 9.2G 5.3G 3.5G 61% /media/disk-1
/dev/sda1 vfat 15G 8.3G 6.4G 57% /media/disk-2
/dev/sda6 ext3 38G 3.9G 33G 11% /media/_home
The above makes no mention of anything on /dev/sdb. So you haven't
mounted it, or it can't yet be mounted.
[root@pc1 ~]# fdisk /dev/sdb
The number of cylinders for this disk is set to 19457.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe2c5e2d5
Device Boot Start End Blocks Id System
/dev/sdb1 1 19457 156288321 83 Linux
What steps have you gone through?
To make use of a drive, you partition it (even if that means using the
whole drive as one partition), fdisk is one tool that you can use. A
quick glance at the above looks like you've done that okay.
Then you format it with a file system (e.g. man mkfs.ext3).
Then you mount it (e.g. man fstab &/or man mount).
--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
8:42 p.m.
On Sat, 2007-12-08 at 18:23 -0700, Karl Larsen wrote:
you must transfer some or all of your system to the new /dev/sdb
hard
drive.
Why do you say that? The original poster just said that they've added a
drive, they didn't mention anything about using it to replace their
existing system. They may well want something extra to their existing
drive space.
To the original poster, unless you do intend to use the new drive to
replace part or all of your existing drive, completely ignore what Karl
has just said.
--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
3:39 p.m.
New subject: [Fedora] Re: large disk space problem?
John Summerfield wrote:
be fair, everywhere else but computing, K means 10^3, M 10^6 etc.
It's
early computer types that sought to redefine it.
And in 2000, the International
Electrotechnical Commission redefined it:
http://en.wikipedia.org/wiki/Binary_prefix
http://en.wikipedia.org/wiki/Kibibyte
9:09 a.m.
New subject: [Fedora] Re: large disk space problem?
On Sun, 2007-12-09 at 15:02 -0700, Ashley M. Kirchner wrote:
John Summerfield wrote:
>> http://en.wikipedia.org/wiki/Binary_prefix
> On reading that, it seems to me that IEC didn't redefine anything,
> they sought to correct the earlier mistake and introduce
alternative
> terminology.
You are correct in that they didn't redefine anything. They're
trying to point out that kilo = kilo (10^3), and kibi = 2^10. What I
meant with redefining is, what people *think* a kilo is when it comes
to
computer terms. Wrong choice of words.
One note. Disk sizes unlike RAM sizes do not have to be powers of 2.
--
=======================================================================
People don't change; they only become more so.
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
4:02 p.m.
New subject: [Fedora] Re: large disk space problem?
John Summerfield wrote:
> http://en.wikipedia.org/wiki/Binary_prefix
On reading that, it seems to me that IEC didn't redefine anything,
they sought to correct the earlier mistake and introduce alternative
terminology.
You are correct in that they didn't redefine anything.
They're
trying to point out that kilo = kilo (10^3), and kibi = 2^10. What I
meant with redefining is, what people *think* a kilo is when it comes to
computer terms. Wrong choice of words.
3:53 p.m.
New subject: [Fedora] Re: large disk space problem?
Ashley M. Kirchner wrote:
John Summerfield wrote:
> be fair, everywhere else but computing, K means 10^3, M 10^6 etc. It's
> early computer types that sought to redefine it.
And in 2000, the International Electrotechnical Commission redefined it:
http://en.wikipedia.org/wiki/Binary_prefix
On reading that, it seems to me that IEC didn't redefine anything, they
sought to correct the earlier mistake and introduce alternative terminology.
btw I suspect Seymour Cray is more famous outside IBM circles than Gene
Amdahl. Gene was IBM's equivalent, bot were lead developers (Gene the
S/360, Seymour the 7600 etc), both were dissatisfied and left to
establish their own companies, and both companies had significant
effects in computing.
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- 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:-)
3:25 p.m.
Mikkel L. Ellertson wrote:
>
Unless you specify otherwise when you create the file system, 5% is
reserved for root. You also lose disk space because of file system
overhead. Then you have the fact that hard drive size is usually
given with k=1000 - it looks better when advertising drive size.
be fair, everywhere else but computing, K means 10^3, M 10^6 etc. It's
early computer types that sought to redefine it.
I remember when 64K[1] was a lot of memory on big computers, and some
manufacturers called it 65K.
[1] words.
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- 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:-)
6:14 a.m.
Tim wrote:
On Sat, 2007-12-08 at 18:23 -0700, Karl Larsen wrote:
> you must transfer some or all of your system to the new /dev/sdb hard
> drive.
>
Why do you say that? The original poster just said that they've added a
drive, they didn't mention anything about using it to replace their
existing system. They may well want something extra to their existing
drive space.
To the original poster, unless you do intend to use the new drive to
replace part or all of your existing drive, completely ignore what Karl
has just said.
If you read what he said, and look at his df data you see two
partitions are almost full, like 96%. I thought his plan was to move
some partitions to the new hard drive. That is why I said that.
Karl
--
Karl F. Larsen, AKA K5DI
Linux User
#450462 http://counter.li.org.
GPG DF28 8F18 94F8 D5C6 9E44 163F 7FD1 3D06 C325 DA40
5:34 a.m.
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(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- 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:-)
11:16 p.m.
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(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- 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:-)
11:09 p.m.
Mikkel L. Ellertson wrote:
Tim wrote:
> On Sun, 2007-12-09 at 09:14 +0800, zhu blue wrote:
>> I recently added additional 160GB disk to my F8 system. and partitioned
>> it as a single partition. but when I use "df" command to show my
>> disk, it only show the size is 9.2G on my Desktop. GNOME it can show
>> the disk as 149.0Gb correctly.
>>
>> [root@pc1 ~]# df
>> Filesystem Type Size Used Avail Use% Mounted on
>> /dev/sda7 ext3 38G 15G 22G 41% /
>> tmpfs tmpfs 474M 12K 474M 1% /dev/shm
>> /dev/sda9 ext3 66G 61G 1.3G 98% /home
>> /dev/sda5 vfat 25G 18G 7.1G 72% /media/disk
>> /dev/sdb1 ext3 9.2G 5.3G 3.5G 61% /media/disk-1
^^^^^^^^^
^^^^^^^^^^^^^^^
That's what you were supposed to see, Tim. That's the new drive.
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- 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:-)
10 p.m.
Tim wrote:
zhu blue:
>>> Disk /dev/sdb: 160.0 GB, 160041885696 bytes
>>> 255 heads, 63 sectors/track, 19457 cylinders
>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>> Disk identifier: 0xe2c5e2d5
>>>
>>> Device Boot Start End Blocks Id System
>>> /dev/sdb1 1 19457 156288321 83 Linux
Tim:
>> To make use of a drive, you partition it (even if that means using the
>> whole drive as one partition), fdisk is one tool that you can use. A
>> quick glance at the above looks like you've done that okay.
Mikkel L. Ellertson:
> 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.
I was never too good at figuring out fdisk block counts, but I thought:
156288321 blocks times 512 byte blocks times two (to make it kilobytes)
divided by 2
gave 160,039,240,704 kilobytes (approx 160 GB).
How is it supposed to be worked out?
You are assuming a block size of 512. You would get a better size
estimate by taking the number of cylinders (end + 1 - start) times
the bytes/cylinder. Then again, the fdisk man page says it does not
work well with large disks, and recommends using parted instead.
The partition is approx 160 GB, but from the output of df, the file
system is only 9.2 GB. So the file system is only a fraction of the
size of the partition. Unless there is a bug in df so that it is
mis-reporting the size of the file system, then the file system does
not fill the partition.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
9:22 p.m.
zhu blue:
>> Disk /dev/sdb: 160.0 GB, 160041885696 bytes
>> 255 heads, 63 sectors/track, 19457 cylinders
>> Units = cylinders of 16065 * 512 = 8225280 bytes
>> Disk identifier: 0xe2c5e2d5
>>
>> Device Boot Start End Blocks Id System
>> /dev/sdb1 1 19457 156288321 83 Linux
Tim:
> To make use of a drive, you partition it (even if that means
using the
> whole drive as one partition), fdisk is one tool that you can use. A
> quick glance at the above looks like you've done that okay.
Mikkel L. Ellertson:
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.
I was never too good at figuring out fdisk block counts, but I thought:
156288321 blocks times 512 byte blocks times two (to make it kilobytes)
gave 160,039,240,704 kilobytes (approx 160 GB).
How is it supposed to be worked out?
--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
9:03 p.m.
Tim wrote:
On Sun, 2007-12-09 at 09:14 +0800, zhu blue wrote:
> I recently added additional 160GB disk to my F8 system. and partitioned
> it as a single partition. but when I use "df" command to show my
> disk, it only show the size is 9.2G on my Desktop. GNOME it can show
> the disk as 149.0Gb correctly.
>
> [root@pc1 ~]# df
> Filesystem Type Size Used Avail Use% Mounted on
> /dev/sda7 ext3 38G 15G 22G 41% /
> tmpfs tmpfs 474M 12K 474M 1% /dev/shm
> /dev/sda9 ext3 66G 61G 1.3G 98% /home
> /dev/sda5 vfat 25G 18G 7.1G 72% /media/disk
> /dev/sdb1 ext3 9.2G 5.3G 3.5G 61% /media/disk-1
^^^^^^^^^
> /dev/sda1 vfat 15G 8.3G 6.4G 57% /media/disk-2
> /dev/sda6 ext3 38G 3.9G 33G 11% /media/_home
The above makes no mention of anything on /dev/sdb. So you haven't
mounted it, or it can't yet be mounted.
>
> Disk /dev/sdb: 160.0 GB, 160041885696 bytes
> 255 heads, 63 sectors/track, 19457 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0xe2c5e2d5
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 1 19457 156288321 83 Linux
What steps have you gone through?
To make use of a drive, you partition it (even if that means using the
whole drive as one partition), fdisk is one tool that you can use. A
quick glance at the above looks like you've done that okay.
Then you format it with a file system (e.g. man mkfs.ext3).
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
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
7:36 p.m.
zhu blue wrote:
hello:
I recently added additional 160GB disk to my F8 system. and partitioned
it as a single partition.
but when I use "df" command to show my disk, it only show the size is
9.2G
on my Desktop. GNOME it can show the disk as 149.0Gb correctly.
how to fix this problem?
the following is my disk info.
---------------------------------------------------------------------
[root@pc1 ~]# df
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda7 ext3 38G 15G 22G 41% /
tmpfs tmpfs 474M 12K 474M 1% /dev/shm
/dev/sda9 ext3 66G 61G 1.3G 98% /home
/dev/sda5 vfat 25G 18G 7.1G 72% /media/disk
/dev/sdb1 ext3 9.2G 5.3G 3.5G 61% /media/disk-1
/dev/sda1 vfat 15G 8.3G 6.4G 57% /media/disk-2
/dev/sda6 ext3 38G 3.9G 33G 11% /media/_home
[root@pc1 ~]# fdisk /dev/sdb
The number of cylinders for this disk is set to 19457.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe2c5e2d5
Device Boot Start End Blocks Id System
/dev/sdb1 1 19457 156288321 83 Linux
Command (m for help): q
[root@pc1 ~]#
------------------------------------------------------------------
thanks,
zhu
What did you use to partition the drive? It might help to try and wipe
all the partition data and start over by repartitioning and reformatting
the drive...
Endy
7:23 p.m.
zhu blue wrote:
hello:
I recently added additional 160GB disk to my F8 system. and partitioned
it as a single partition.
but when I use "df" command to show my disk, it only show the size is
9.2G
on my Desktop. GNOME it can show the disk as 149.0Gb correctly.
how to fix this problem?
the following is my disk info.
---------------------------------------------------------------------
[root@pc1 ~]# df
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda7 ext3 38G 15G 22G 41% /
tmpfs tmpfs 474M 12K 474M 1% /dev/shm
/dev/sda9 ext3 66G 61G 1.3G 98% /home
/dev/sda5 vfat 25G 18G 7.1G 72% /media/disk
/dev/sdb1 ext3 9.2G 5.3G 3.5G 61% /media/disk-1
/dev/sda1 vfat 15G 8.3G 6.4G 57% /media/disk-2
/dev/sda6 ext3 38G 3.9G 33G 11% /media/_home
[root@pc1 ~]# fdisk /dev/sdb
The number of cylinders for this disk is set to 19457.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe2c5e2d5
Device Boot Start End Blocks Id System
/dev/sdb1 1 19457 156288321 83 Linux
Command (m for help): q
[root@pc1 ~]#
------------------------------------------------------------------
thanks,
zhu
I see nothing wrong. But you must transfer some or all of your
system to the new /dev/sdb hard drive. Do so with care.
Karl
--
Karl F. Larsen, AKA K5DI
Linux User
#450462 http://counter.li.org.
GPG DF28 8F18 94F8 D5C6 9E44 163F 7FD1 3D06 C325 DA40
6032
days inactive
6033
days old
18 comments
8 participants
participants (8)
-
Aaron Konstam -
Ashley M. Kirchner -
Endy -
John Summerfield -
Karl Larsen -
Mikkel -
Tim -
zhu blue