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

Re: FDISK parameters was Re: undelete for partition tables?



Mirek Kwasniak wrote:
> 
> On Tue, Sep 14, 1999 at 12:54:47PM +0000, Ed Cogburn wrote:
> >
> >       I just tried (as root) the three fdisk examples (-l is lowercase
> > L) given above.  Only the last one worked: "fdisk -l /dev/hda".
> > The -u does nothing at all.  Does anybody else see this behavior,
> > or has my fdisk been lobotomized somehow?
> 
> Hi,
> $ fdisk -v
> fdisk v2.9w
> 
> $fdisk -l  /dev/hda
> 
> Disk /dev/hda: 255 heads, 63 sectors, 1027 cylinders
> Units = cylinders of 16065 * 512 bytes
> 
>    Device Boot    Start       End    Blocks   Id  System
> /dev/hda1           646      1027   3068415   83  Linux
> /dev/hda2   *       608       645    305235   83  Linux
> /dev/hda3             1       607   4875696   83  Linux
> $ fdisk -l -u /dev/hda
> 
> Disk /dev/hda: 255 heads, 63 sectors, 1027 cylinders
> Units = sectors of 1 * 512 bytes
> 
>    Device Boot    Start       End    Blocks   Id  System
> /dev/hda1      10361925  16498754   3068415   83  Linux
> /dev/hda2   *   9751455  10361924    305235   83  Linux
> /dev/hda3            63   9751454   4875696   83  Linux
> 
> Do you see a difference? To see all disks you can use
> 
>    fdisk -l -u /dev/hd? /dev/sd?
> 
> or try another program
> 
>   sfdisk -l -uS
> 
> Mirek


	OK, I'm wrong about -u, it does work; I should have looked
closer.  The use of 'fdisk -l', without a device parameter, still
doesn't work even though the man page says it should.
	According to Tom's examples and the man page, "fdisk -l" and
"fdisk -l -u" should work without a device parameter, but I get:

**********************************
08:00pm /home/ed\> fdisk -v
fdisk v2.9w
08:00pm /home/ed\> fdisk -l

Usage: fdisk [-l] [-b SSZ] [-u] device
E.g.: fdisk /dev/hda  (for the first IDE disk)
  or: fdisk /dev/sdc  (for the third SCSI disk)
  or: fdisk /dev/eda  (for the first PS/2 ESDI drive)
  or: fdisk /dev/rd/c0d0  or: fdisk /dev/ida/c0d0  (for RAID
devices)
  ...
**********************************

	Oh, well.

-- 
Ed C.


Reply to: