Problem z mke2fs

Radoslaw Kojdecki radek w media-com.com.pl
Czw, 6 Cze 2002, 11:53:16 CEST


[root w radko radek]# uname -a
Linux radko 2.5.17 #1 czw maj 23 13:54:18 CEST 2002 i686 Pentium_II_(Deschutes)

[root w radko radek]# dmesg | grep hda
Kernel command line: auto BOOT_IMAGE=pld25 ro root=301 hda=19773,16,63
ide_setup: hda=19773,16,63
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
hda: SAMSUNG SV1021D, ATA DISK drive
hda: 19931184 sectors w/444KiB Cache, CHS=19773/16/63, UDMA(33)
 hda: hda1 hda2 hda3

[root w radko radek]# fdisk /dev/hda

Command (m for help): p

Disk /dev/hda: 1 heads, 19931184 sectors, 1 cylinders
Units = cylinders of 19931184 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1         1   2015968+  83  Linux
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 1, 1) logical=(0, 0, 64)
Partition 1 has different physical/logical endings:
     phys=(1023, 15, 63) logical=(0, 0, 4032000)
Partition 1 does not end on cylinder boundary:
     phys=(1023, 15, 63) should be (1023, 0, 19931184)
/dev/hda2             1         1   2016000    c  Win95 FAT32 (LBA)
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(1023, 15, 63) logical=(0, 0, 4032001)
Partition 2 has different physical/logical endings:
     phys=(1023, 15, 63) logical=(0, 0, 8064000)
Partition 2 does not end on cylinder boundary:
     phys=(1023, 15, 63) should be (1023, 0, 19931184)
/dev/hda3             1         1   5933592   83  Linux
Partition 3 has different physical/logical beginnings (non-Linux?):
     phys=(1023, 15, 63) logical=(0, 0, 8064001)
Partition 3 has different physical/logical endings:
     phys=(1023, 15, 63) logical=(0, 0, 19931184)
Partition 3 does not end on cylinder boundary:
     phys=(1023, 15, 63) should be (1023, 0, 19931184)

Po zrobieniu (w trybie x) c-19773 h-16 s-63

Wychodzi wszystko OK :

Command (m for help): p

Disk /dev/hda: 16 heads, 63 sectors, 19773 cylinders
Units = cylinders of 1008 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1      4000   2015968+  83  Linux
/dev/hda2          4001      8000   2016000    c  Win95 FAT32 (LBA)
/dev/hda3          8001     19773   5933592   83  Linux


No ale to nie koniec problemow (to w zasadzie nie jest problem).

[root w radko radek]# mke2fs /dev/hda3
mke2fs 1.27 (8-Mar-2002)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
741888 inodes, 1483398 blocks
74169 blocks (5.00%) reserved for the super user
First data block=0
46 block groups
32768 blocks per group, 32768 fragments per group
16128 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Przekroczony limit wielkości pliku


To samo przy innym :

[root w radko radek]# mkreiserfs /dev/hda3

<-------------mkreiserfs, 2002------------->
reiserfsprogs 3.x.1b

mkreiserfs: Guessing about desired format..
mkreiserfs: Kernel 2.5.17 is running.
Format 3.6 with standard journal
Count of blocks on the device: 1483398
Number of blocks consumed by mkreiserfs formatting process: 8257
Blocksize: 4096
Hash function used to sort names: "r5"
Journal Size 8193 blocks (first block 18)
Journal Max transaction length 1024
inode generation number: 0
UUID: 2dd6a639-5e63-4cdb-bac8-b00552c41ffc
ATTENTION: YOU SHOULD REBOOT AFTER FDISK!
        ALL DATA WILL BE LOST ON '/dev/hda3'!
Continue (y/n):y
Initializing journal - 0%....20%....40%....60%....80%....100%
Przekroczony limit wielkości pliku


Pomozcie ;))

pozdrawiem,

Radek
-- 
---------------------------------------------------------------------
Media-Com Sp. z o.o.                       43-100 Tychy, ul. Długa 19
http://www.media-com.com.pl/           e-mail : info w media-com.com.pl
---------------------------------------------------------------------



Więcej informacji o liście dyskusyjnej pld-users-pl