Dotaz: Freebsd - problemove pridani slice

[PanZvedavy]

Dotaz ohledne pridani slice. Pouzivam gmirror na system(8.1 - 64bit) a presel jsem z 2x500GB na 2x1TB Hdd. Migrace probehla v poradku a vse bezi uz nejakou dobu jak ma. Ted bych rad pouzil zbyvajici prostor cca 500GB na obou discich. Pres sysinstall jsem zavolal fdisk na jeden z disku a vytvoril novou slice a dal zapsat...nasledovalo "Wrote FDISK partition information out successfully." Dam Q pro ukonceni a vyskoci hlaska: "chunk 'mirror/gm0s1' [67134856..1043904936] does not start on a track boundary "chunk 'ad10s1' [1043904937..1953525167] does not start on a track boundary"... na cemz skoncim protoze nejsem schopny vytvorit prostor pro newfs. Co jsem opomel nebo delam spatne? df... Filesystem Size Used Avail Capacity Mounted on /dev/mirror/gm0s1a 1.9G 1.4G 388M 79% / devfs 1.0K 1.0K 0B 100% /dev /dev/mirror/gm0s1e 1.9G 27M 1.8G 1% /tmp /dev/mirror/gm0s1f 9.7G 3.5G 5.4G 40% /usr /dev/mirror/gm0s1d 3.9G 540M 3.0G 15% /var

Odpovědi

[martin-ux]

tazko sa luska co si to poslal, posli vystup z commandov:

# gmirror list
# gpart show

len ich pls obal do <pre></pre> tagov.

[PanZvedavy]

gpart show
=>       63  976770963  mirror/gm0  MBR  (466G)
         63  976770081           1  freebsd  [active]  (466G)
  976770144        882              - free -  (441K)

=>        0  976770081  mirror/gm0s1  BSD  (466G)
          0    4194304             1  freebsd-ufs  (2.0G)
    4194304    8388608             2  freebsd-swap  (4.0G)
   12582912    8388608             4  freebsd-ufs  (4.0G)
   20971520    4194304             5  freebsd-ufs  (2.0G)
   25165824   20971520             6  freebsd-ufs  (10G)
   46137344  930632737             7  freebsd-ufs  (444G)

gmirror list

Geom name: gm0
State: COMPLETE
Components: 2
Balance: round-robin
Slice: 4096
Flags: NONE
GenID: 3
SyncID: 8
ID: 1156219537
Providers:
1. Name: mirror/gm0
   Mediasize: 500106779648 (466G)
   Sectorsize: 512
   Mode: r6w6e17
Consumers:
1. Name: ad4
   Mediasize: 1000204886016 (932G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Priority: 0
   Flags: DIRTY
   GenID: 3
   SyncID: 8
   ID: 2930723184
2. Name: ad10
   Mediasize: 1000204886016 (932G)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
   Priority: 0
   Flags: DIRTY
   GenID: 3
   SyncID: 8
   ID: 2784431393

[martin-ux]

posli este:

# fdisk /dev/ad4
# fdisk /dev/gm0

gpart output ti nezobrazil informacie o ad4 a ad10 ?

ako si to migroval na vacsie disky ? vyzera to, ako keby si gmirror ponechal stare informacie (restore pomocou dd ?), pricom gm0 mas priamo na diskoch, nie na slice-och (co aj bolo asi recommended, no nie nutnost).

[PanZvedavy]

Pri prechodu na vetsi disky jsem jednoduse vymenil vetsi disky za mensi. Takze z 500GB jsem, mirroroval na 1TB a z toho na dalsi 1TB .

******* Working on device /dev/ad4 *******
parameters extracted from in-core disklabel are:
cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 1043904937, size 909619223 (444150 Meg), flag 80 (active)
        beg: cyl 1023/ head 255/ sector 63;
        end: cyl 1023/ head 15/ sector 63
The data for partition 2 is:

The data for partition 3 is:

The data for partition 4 is:

fdisk /dev/mirror/gm0
******* Working on device /dev/mirror/gm0 *******
parameters extracted from in-core disklabel are:
cylinders=60801 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=60801 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 1043904937, size 909619223 (444150 Meg), flag 80 (active)
        beg: cyl 1023/ head 255/ sector 63;
        end: cyl 1023/ head 15/ sector 63
The data for partition 2 is:

The data for partition 3 is:

The data for partition 4 is:

[martin-ux]

to ako za chodu si vybral stary a pridal ten vacsi ? to tak nemozes a preto to mas aj zle; ako ti ukazuje fdisk aj gpart.

musis ten mirror rozbit, ten volny disk nanovo naformatovat, na-sliceovat, pridat do mirroru a to iste spravit potom s opacnou stranou. pri tejto migracii by som ti aj odporucil pouzit GPT layout miesto MBR (teraz je uz aj na to tool gdisk(8), netreba to robit rucne, i ked ja som ho este nikdy nepouzil)

jedna sa o server, ktory nemozes rebootovat alebo o desktop?

je piatok polnoc, co je magicka doba, kedy nie je dobre robit taketo "migracie":). V principe ide o to, ze

• rozbijes mirror: vyberes /dev/ad4 z mirroru von
• clearnes /dev/ad4 (dd, gmirror clear)
• vytvorit nove slice-y (alebo particie v pripadne GPT) - 2 x 500 GB napr.
• slice1 alebo p1 vlozis spat do mirroru

zmirrorujes a toto spravis aj s druhym providerom. tym, ze mas mirror tak sa vzdy mozes hrat s jednou stranou a data nestratis.

na druhej particii alebo slicei potom vytvoris uplne novy mirror (gm1), ktory potom budes pouzivat dalej.

ja osobne pouzivam GPT, kde kazdy FS mam zvlast v mirrore:

# gmirror status
        Name    Status  Components
mirror/groot  COMPLETE  ad6p2
                        ad8p2
 mirror/gtmp  COMPLETE  ad6p4
                        ad8p4
 mirror/gvar  COMPLETE  ad6p5
                        ad8p5
 mirror/gusr  COMPLETE  ad6p6
                        ad8p6

ak chces, zajtra ti poslem command-by-command postup, ako to spravit. v tuto nocnu dobu by som sa mohol pomylit, co by som nerad.

[PanZvedavy]

Mno potreboval jsem vyzkouset krizovy scenar selhani disku a nahrazeni jinym typem, coz me prijeme prekvapilo, ze to slo bez problemu. Tech 500GB na kazdem disku, ale momentalne potrebuji(bez raidu). Nicmene z toho rozbijeni mirroru nejsem moc nadsen, protoze se jedna o produkcni masinu se spoustou virtualu... Pokud, ale nebude jina cesta, tak mi nic jineho nakonec nezbyde.

[martin-ux]

no vymenit disk za disk sa da bez problemov, ale zvacsit mirror tymto postupom nemozes (da sa u ZFS).

tvoje providers pre gmirror su cele disky -- toto je dost velky problem pre to, co chces ty teraz dosiahnut. i ked rozbijes mirror a ten disk nasliceujes, nemas ho ako pridat spat. zostanu ti stale dva problemy:

• pridas len slice1 a vznikne ti nebootovatelny system (lava strana mirroru je cely disk, prava slice)
• pridas cely disk a stratis svoje zmeny (pri syncovani zmiznu)

toto som si vcera uz neuvedomil, ja som vzdy pouzival slicey, teraz particie. nepoznam ani sposob na nefresh providerov, nikdy som sa s tym nestretol (geom uklada metadata na konci provideru).

toto sa ti skompikovalo na tolko, ze budes musiet IMHO za behu rozbit mirror a na volnom disku vytvorit novy mirror, nasliceovat a data prekopirovat (dump/restore). potom urobit reboot, zmazat stary mirror, slicenut a pridat slice do noveho mirroru.

[PanZvedavy]

jop uz mi to docvaklo taky :( Zatim to ale necham. Thx za namety.

[martin-ux]

np

ono je vzdy lepsie mat system na osobitnych diskoch oddeleny od aplikacii. clovek sa tym vyhne vela neprijemnostiam. ta migracia na novy mirror je online, reboot je vsak potrebny. mam to odskusane na niekolkych live systemoch - vzdy bez problemov.

ale jj, tie virtualy by so syncovanim robili problemy.