Nová čísla časopisů od nakladatelství Raspberry Pi: MagPi 140 (pdf) a HackSpace 77 (pdf).
ESPHome, tj. open source systém umožňující nastavovat zařízení s čipy ESP (i dalšími) pomocí konfiguračních souborů a připojit je do domácí automatizace, například do Home Assistantu, byl vydán ve verzi 2024.4.0.
LF AI & Data Foundation patřící pod Linux Foundation spustila Open Platform for Enterprise AI (OPEA).
Neziskové průmyslové konsorcium Khronos Group vydalo verzi 1.1 specifikace OpenXR (Wikipedie), tj. standardu specifikujícího přístup k platformám a zařízením pro XR, tj. platformám a zařízením pro AR (rozšířenou realitu) a VR (virtuální realitu). Do základu se z rozšíření dostalo XR_EXT_local_floor. Společnost Collabora implementuje novou verzi specifikace do platformy Monado, tj. open source implementace OpenXR.
Byla vydána nová verze 0.38.0 multimediálního přehrávače mpv (Wikipedie) vycházejícího z přehrávačů MPlayer a mplayer2. Přehled novinek, změn a oprav na GitHubu. Požadován je FFmpeg 4.4 nebo novější a také libplacebo 6.338.2 nebo novější.
ClamAV (Wikipedie), tj. multiplatformní antivirový engine s otevřeným zdrojovým kódem pro detekci trojských koní, virů, malwaru a dalších škodlivých hrozeb, byl vydán ve verzích 1.3.1, 1.2.3 a 1.0.6. Ve verzi 1.3.1 je mimo jiné řešena bezpečnostní chyba CVE-2024-20380.
Digitální a informační agentura (DIA) oznámila (PDF, X a Facebook), že mobilní aplikace Portál občana je ode dneška oficiálně venku.
#HACKUJBRNO 2024, byly zveřejněny výsledky a výstupy hackathonu města Brna nad otevřenými městskými daty, který se konal 13. a 14. dubna 2024.
Společnost Volla Systeme stojící za telefony Volla spustila na Kickstarteru kampaň na podporu tabletu Volla Tablet s Volla OS nebo Ubuntu Touch.
Společnost Boston Dynamics oznámila, že humanoidní hydraulický robot HD Atlas šel do důchodu (YouTube). Nastupuje nová vylepšená elektrická varianta (YouTube).
Řešení dotazu:
zase takovy expert nejsem. Hlavne se bojim, abych si nezlikvidoval system, ktery jsem tak nejak ladil skoro dva roky. Nevite o nejakem navodu, ktery by mi v tehle situaci pomohl?
AbcLinuxu.cz
ITBiz.cz
HDmag.cz
AbcPráce.cz
18.12.2012 08:09
cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sda2[0]
1464894976 blocks [2/1] [U_]
md0 : active raid1 sdb1[1] sda1[0]
240832 blocks [2/2] [UU]
unused devices: none
fdisk -l Disk /dev/sda: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0003dda6 Device Boot Start End Blocks Id System /dev/sda1 * 1 30 240943+ fd Linux raid autodetect /dev/sda2 31 182401 1464895057+ fd Linux raid autodetect Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 * 1 30 240943+ fd Linux raid autodetect Partition 1 does not start on physical sector boundary. /dev/sdb2 31 182401 1464895057+ fd Linux raid autodetect Partition 2 does not start on physical sector boundary. Disk /dev/md0: 246 MB, 246611968 bytes 2 heads, 4 sectors/track, 60208 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 512 bytes Disk identifier: 0x00000000 Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 1500.1 GB, 1500052455424 bytes 2 heads, 4 sectors/track, 366223744 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/md1 doesn't contain a valid partition table Disk /dev/dm-0: 16.1 GB, 16106127360 bytes 255 heads, 63 sectors/track, 1958 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 2826 MB, 2826960896 bytes 255 heads, 63 sectors/track, 343 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 53.7 GB, 53687091200 bytes 255 heads, 63 sectors/track, 6527 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table Disk /dev/dm-3: 20 MB, 20971520 bytes 255 heads, 63 sectors/track, 2 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-3 doesn't contain a valid partition table Disk /dev/dm-4: 3221 MB, 3221225472 bytes 255 heads, 63 sectors/track, 391 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-4 doesn't contain a valid partition table Disk /dev/dm-5: 8808 MB, 8808038400 bytes 255 heads, 63 sectors/track, 1070 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-5 doesn't contain a valid partition table Disk /dev/dm-6: 104 MB, 104857600 bytes 255 heads, 63 sectors/track, 12 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-6 doesn't contain a valid partition table Disk /dev/dm-7: 369 MB, 369098752 bytes 255 heads, 63 sectors/track, 44 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-7 doesn't contain a valid partition table Disk /dev/dm-8: 1610 MB, 1610612736 bytes 255 heads, 63 sectors/track, 195 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-8 doesn't contain a valid partition table Disk /dev/dm-9: 375.8 GB, 375809638400 bytes 255 heads, 63 sectors/track, 45689 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-9 doesn't contain a valid partition table Disk /dev/dm-10: 21.5 GB, 21474836480 bytes 255 heads, 63 sectors/track, 2610 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-10 doesn't contain a valid partition table Disk /dev/dm-11: 75.2 GB, 75161927680 bytes 255 heads, 63 sectors/track, 9137 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-11 doesn't contain a valid partition table Disk /dev/dm-12: 45.1 GB, 45097156608 bytes 255 heads, 63 sectors/track, 5482 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-12 doesn't contain a valid partition table Disk /dev/dm-13: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-13 doesn't contain a valid partition table Disk /dev/dm-14: 80.5 GB, 80530636800 bytes 255 heads, 63 sectors/track, 9790 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-14 doesn't contain a valid partition table Disk /dev/dm-15: 5368 MB, 5368709120 bytes 255 heads, 63 sectors/track, 652 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-15 doesn't contain a valid partition table Disk /dev/dm-16: 21.5 GB, 21474836480 bytes 255 heads, 63 sectors/track, 2610 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-16 doesn't contain a valid partition table Disk /dev/dm-17: 1610 MB, 1610612736 bytes 255 heads, 63 sectors/track, 195 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-17 doesn't contain a valid partition table Disk /dev/dm-18: 159 MB, 159383552 bytes 255 heads, 63 sectors/track, 19 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-18 doesn't contain a valid partition table Disk /dev/dm-19: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-19 doesn't contain a valid partition table Disk /dev/dm-20: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-20 doesn't contain a valid partition table Disk /dev/dm-21: 53.7 GB, 53687091200 bytes 255 heads, 63 sectors/track, 6527 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-21 doesn't contain a valid partition table Disk /dev/dm-22: 16.1 GB, 16106127360 bytes 255 heads, 63 sectors/track, 1958 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x08040000 Disk /dev/dm-22 doesn't contain a valid partition table Disk /dev/dm-23: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-23 doesn't contain a valid partition table Disk /dev/dm-24: 16.1 GB, 16105074688 bytes 255 heads, 63 sectors/track, 1957 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Alignment offset: 1024 bytes Disk identifier: 0x00000000 Disk /dev/dm-24 doesn't contain a valid partition table
vgs VG #PV #LV #SN Attr VSize VFree LVM-sda2-sdb2 1 24 0 wz--n- 1,36t 604,59g
lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert home LVM-sda2-sdb2 -wi-ao 50,00g mountpoint LVM-sda2-sdb2 -wi-ao 20,00m root LVM-sda2-sdb2 -wi-ao 15,00g root-ss LVM-sda2-sdb2 -wi-a- 1,00g shares-AUDIO-DA LVM-sda2-sdb2 -wi-ao 70,00g shares-CRYPT LVM-sda2-sdb2 -wi-ao 15,00g shares-DOWNLOAD LVM-sda2-sdb2 -wi-ao 50,00g shares-FAX LVM-sda2-sdb2 -wi-ao 100,00m shares-FILMY LVM-sda2-sdb2 -wi-ao 350,00g shares-FOTKY LVM-sda2-sdb2 -wi-ao 42,00g shares-FOTKY-DA LVM-sda2-sdb2 -wi-ao 30,00g shares-PUBLIC LVM-sda2-sdb2 -wi-ao 20,00g shares-PUBLIC-Fermont LVM-sda2-sdb2 -wi-a- 352,00m shares-vmail LVM-sda2-sdb2 -wi-a- 1,50g swap LVM-sda2-sdb2 -wi-ao 2,63g sysdata-PXEboot LVM-sda2-sdb2 -wi-ao 20,00g sysdata-WIN_profiles LVM-sda2-sdb2 -wi-ao 5,00g sysdata-partimag LVM-sda2-sdb2 -wi-ao 75,00g sysdata-uloziste LVM-sda2-sdb2 -wi-ao 152,00m sysdata-vmail LVM-sda2-sdb2 -wi-ao 1,50g sysdata-zaloha LVM-sda2-sdb2 -wi-ao 30,00g var-lib-mysql LVM-sda2-sdb2 -wi-ao 8,20g var-log LVM-sda2-sdb2 -wi-ao 3,00g var-www LVM-sda2-sdb2 -wi-ao 2,00g
lvdisplay --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/root VG Name LVM-sda2-sdb2 LV UUID Xzlzn6-cKxT-PPN0-7gyw-jWqA-sZRJ-kb9SSe LV Write Access read/write LV Status available # open 1 LV Size 15,00 GiB Current LE 3840 Segments 2 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/home VG Name LVM-sda2-sdb2 LV UUID 6ymEvq-B3xX-dIj0-13a2-WpDR-0oB6-rJcLRz LV Write Access read/write LV Status available # open 1 LV Size 50,00 GiB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:2 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/swap VG Name LVM-sda2-sdb2 LV UUID nmykvg-jgxP-3343-xIYh-FoGs-rN6G-BC8aZk LV Write Access read/write LV Status available # open 1 LV Size 2,63 GiB Current LE 674 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/mountpoint VG Name LVM-sda2-sdb2 LV UUID wQIJVI-hDOO-fWB4-Xlku-9frQ-1mMk-nJvLnM LV Write Access read/write LV Status available # open 1 LV Size 20,00 MiB Current LE 5 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:3 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/var-log VG Name LVM-sda2-sdb2 LV UUID df32Un-Ly24-Cg4h-t40P-Pqar-sVIo-MP1K08 LV Write Access read/write LV Status available # open 1 LV Size 3,00 GiB Current LE 768 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:4 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/var-lib-mysql VG Name LVM-sda2-sdb2 LV UUID z3XEPe-qQUM-WXWX-HnHl-elPN-CTfS-VgnSbH LV Write Access read/write LV Status available # open 1 LV Size 8,20 GiB Current LE 2100 Segments 3 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:5 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-FAX VG Name LVM-sda2-sdb2 LV UUID SkCHWn-XSgf-0YRf-0Ni8-8UgV-6wQL-c5xH1o LV Write Access read/write LV Status available # open 1 LV Size 100,00 MiB Current LE 25 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:6 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-PUBLIC-Fermont VG Name LVM-sda2-sdb2 LV UUID PToZ3T-DEXZ-eyak-Tkn1-liX9-kBLh-own2r2 LV Write Access read/write LV Status available # open 0 LV Size 352,00 MiB Current LE 88 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:7 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-vmail VG Name LVM-sda2-sdb2 LV UUID KaZ3m4-T3Lj-iFur-zWo4-Z7C1-u93H-OAai7t LV Write Access read/write LV Status available # open 0 LV Size 1,50 GiB Current LE 384 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:8 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-FILMY VG Name LVM-sda2-sdb2 LV UUID Hb8IJ2-wJZJ-g6cb-C7va-VCPd-n5We-Hs1Nmg LV Write Access read/write LV Status available # open 1 LV Size 350,00 GiB Current LE 89600 Segments 5 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:9 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-PUBLIC VG Name LVM-sda2-sdb2 LV UUID dnN1LZ-2NSC-0gOt-6wFl-cxu3-97x4-Q6Pdly LV Write Access read/write LV Status available # open 1 LV Size 20,00 GiB Current LE 5120 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:10 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-AUDIO-DA VG Name LVM-sda2-sdb2 LV UUID qIQ1V9-631d-I0UI-INqT-waoG-YNyT-eE2EA6 LV Write Access read/write LV Status available # open 1 LV Size 70,00 GiB Current LE 17920 Segments 2 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:11 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-FOTKY VG Name LVM-sda2-sdb2 LV UUID Su3113-thGt-baM0-BXtP-3gjk-0ArK-00dW3E LV Write Access read/write LV Status available # open 1 LV Size 42,00 GiB Current LE 10752 Segments 3 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:12 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-FOTKY-DA VG Name LVM-sda2-sdb2 LV UUID 94rCwN-3iTV-LPo1-vauB-CWg1-sCgN-JYtELh LV Write Access read/write LV Status available # open 1 LV Size 30,00 GiB Current LE 7680 Segments 3 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:13 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/sysdata-partimag VG Name LVM-sda2-sdb2 LV UUID otObP4-qOKI-iAs1-Ah5o-ks2C-ZOaj-8eoUoH LV Write Access read/write LV Status available # open 1 LV Size 75,00 GiB Current LE 19200 Segments 3 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:14 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/sysdata-WIN_profiles VG Name LVM-sda2-sdb2 LV UUID 226ia8-XbIR-isS5-4yMS-7geL-2QaK-P1oMJg LV Write Access read/write LV Status available # open 1 LV Size 5,00 GiB Current LE 1280 Segments 2 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:15 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/sysdata-PXEboot VG Name LVM-sda2-sdb2 LV UUID CeK3fK-j7vx-wbnp-xFao-jH1i-bfsa-WDdRyM LV Write Access read/write LV Status available # open 1 LV Size 20,00 GiB Current LE 5120 Segments 3 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:16 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/sysdata-vmail VG Name LVM-sda2-sdb2 LV UUID 6RqAtr-g0ic-FowL-f5Qv-k942-jsr8-iVDnE8 LV Write Access read/write LV Status available # open 1 LV Size 1,50 GiB Current LE 384 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:17 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/sysdata-uloziste VG Name LVM-sda2-sdb2 LV UUID L4nVad-vl8L-veOi-xVIJ-uXRg-RIhr-IlMg4y LV Write Access read/write LV Status available # open 1 LV Size 152,00 MiB Current LE 38 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:18 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/sysdata-zaloha VG Name LVM-sda2-sdb2 LV UUID tBmz80-DRc7-9d93-XYlr-M6kX-0d51-WR7Zrz LV Write Access read/write LV Status available # open 1 LV Size 30,00 GiB Current LE 7680 Segments 2 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:19 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/var-www VG Name LVM-sda2-sdb2 LV UUID B3JVlJ-gzEf-78ny-KXAC-6erb-bkfH-H2f9aV LV Write Access read/write LV Status available # open 1 LV Size 2,00 GiB Current LE 512 Segments 2 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:20 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-DOWNLOAD VG Name LVM-sda2-sdb2 LV UUID aV9CE5-ftJB-FGIY-zk8s-DaoF-Lac6-oeHhhw LV Write Access read/write LV Status available # open 1 LV Size 50,00 GiB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:21 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/shares-CRYPT VG Name LVM-sda2-sdb2 LV UUID 3FW29F-9vHW-Ovr1-Shxl-0qVm-y20g-oTTMCG LV Write Access read/write LV Status available # open 1 LV Size 15,00 GiB Current LE 3840 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:22 --- Logical volume --- LV Name /dev/LVM-sda2-sdb2/root-ss VG Name LVM-sda2-sdb2 LV UUID EH12qI-fQb2-evmy-jksS-KOHB-3wmK-U0BBfc LV Write Access read/write LV Status available # open 0 LV Size 1,00 GiB Current LE 256 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:23
vgdisplay --- Volume group --- VG Name LVM-sda2-sdb2 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 12183 VG Access read/write VG Status resizable MAX LV 0 Cur LV 24 Open LV 21 Max PV 0 Cur PV 1 Act PV 1 VG Size 1,36 TiB PE Size 4,00 MiB Total PE 357640 Alloc PE / Size 202866 / 792,45 GiB Free PE / Size 154774 / 604,59 GiB VG UUID o0CrBY-gNER-XRDl-OW2n-wLL3-kurA-jAA0px
df -h
Souborový systém Velikost Užito Volno Uži% Připojeno do
/dev/mapper/LVM--sda2--sdb2-root
15G 3,8G 11G 27% /
tmpfs 1,5G 0 1,5G 0% /lib/init/rw
udev 1,5G 260K 1,5G 1% /dev
tmpfs 1,5G 0 1,5G 0% /dev/shm
/dev/md0 221M 34M 176M 16% /boot
/dev/mapper/LVM--sda2--sdb2-home
50G 27G 21G 56% /home
/dev/mapper/LVM--sda2--sdb2-var--lib--mysql
8,1G 3,7G 4,0G 49% /var/lib/mysql
/dev/mapper/LVM--sda2--sdb2-var--log
3,0G 344M 2,5G 12% /var/log
/dev/mapper/LVM--sda2--sdb2-var--www
2,0G 1,3G 648M 67% /var/www
/dev/mapper/LVM--sda2--sdb2-shares--PUBLIC
20G 7,3G 12G 39% /shares/PUBLIC
/dev/mapper/LVM--sda2--sdb2-shares--FOTKY
42G 31G 8,4G 79% /shares/FOTKY
/dev/mapper/LVM--sda2--sdb2-shares--FOTKY--DA
30G 27G 1,3G 96% /shares/FOTKY-DA
/dev/mapper/LVM--sda2--sdb2-shares--AUDIO--DA
69G 55G 11G 84% /shares/AUDIO-DA
/dev/mapper/LVM--sda2--sdb2-shares--FAX
97M 25M 68M 27% /shares/FAX
/dev/mapper/LVM--sda2--sdb2-shares--FILMY
345G 290G 38G 89% /shares/FILMY
/dev/mapper/LVM--sda2--sdb2-shares--DOWNLOAD
50G 2,6G 45G 6% /shares/DOWNLOAD
/dev/mapper/crypt 15G 153M 15G 2% /shares/CRYPT
/dev/mapper/LVM--sda2--sdb2-sysdata--vmail
1,5G 1,1G 363M 75% /sysdata/vmail
/dev/mapper/LVM--sda2--sdb2-sysdata--partimag
74G 52G 19G 74% /sysdata/partimag
/dev/mapper/LVM--sda2--sdb2-sysdata--WIN_profiles
5,0G 603M 4,1G 13% /sysdata/WIN_profiles
/dev/mapper/LVM--sda2--sdb2-sysdata--PXEboot
20G 17G 1,9G 91% /sysdata/PXEboot
/dev/mapper/LVM--sda2--sdb2-sysdata--uloziste
148M 6,5M 134M 5% /sysdata/uloziste
/dev/mapper/LVM--sda2--sdb2-sysdata--zaloha
30G 27G 1,9G 94% /sysdata/zaloha
/dev/mapper/LVM--sda2--sdb2-mountpoint
20M 1,2M 18M 7% /media
/dev/loop0 97M 5,6M 87M 7% /var/spool/havp
Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id SystemTohle je v poradku?
Sector size (logical/physical): 512 bytes / 4096 bytes nebo mam nejak upravit?
hdparm -I /dev/sdb |grep size Logical Sector size: 512 bytes Physical Sector size: 4096 bytes device size with M = 1024*1024: 1430799 MBytes device size with M = 1000*1000: 1500301 MBytes (1500 GB) cache/buffer size = unknown
Rekl bych, ze tady http://askubuntu.com/questions/141669/creating-properly-aligned-partitions-on-a-replacement-disk se pta tazatel v podstate na to same jako ja, ale nejak jsem nepochopil ty odpovedi:(
19.12.2012 22:02
AraxoN | skóre: 47
| blog: slon_v_porcelane
| Košice
Migrací.
1) připojíš nový disk
2) vytvoříš zarovnanou partition (na konci disku necháš třeba 100MiB volného pro sichr)
3) nad partition vytvoříš degradované pole
4) pole připojíš a překopíruješ na něj data ze starého degradovaného pole
5) staré degradované pole zrušíš, vytvoříš na něm obdobnou partition a připojíš jí do stávajícího pole a provede se sync.
Zdar Max
1) disk mám fyzicky připojený jako /dev/sdb
2) dejme tomu, že to se mi nějak povede
3) mám vytvořit md2 a md3 (když už md0 a md1 mám)?
4) ano, ale nevím, co s velikostí LVM, když nový disk bude mít jiné velkosti oddílů?
5) tady už nebude vadit, že disk je 512B?
Napadla me jedna mozna blbost na ukor mista na /dev/md0. Vzhledem k tomu, ze LVM mam jen na /dev/md1:
1) vytvoril bych na /dev/sdb zarovnany oddil /dev/sdb2 o neco vetsi, nez /dev/sda2
2) pridal bych do raidu (/dev/md1)
3) vyřadil bych /dev/sda2 z /dev/md1
4) roztahl bych /dev/md1 na celou /dev/sdb2
---------------------------------------------------
Tím bych měl RAID ve stavu
/dev/md0 >> U_ (/dev/sda1 /dev/sdb1)
/dev/md1 >> _U (/dev/sda2 /dev/sdb2)
---------------------------------------------------
5) zrušil bych /dev/md0
6) vytvořím nové pole /dev/md0 na /dev/sdb1
7) připojím ho a překopíruju do nej data z /dev/sda1
8) na /dev/sdb1 nainstaluju grub
--------------------------------------------------------------------------------------
Teď bych měl mít funkční systém na disku /dev/sdb v degradovaném RAIDU
9) vytvořím oddíly na /dev/sda stejné jako mám teď na /dev/sdb (nebudu mít zase stejný problém?
10) synchronizuju raid
Šlo by to takhle nějak?
parted nebo snad každý moderní grafickou nadstavbu, tak vám to rozdělí správně. Napočítat ručně velikosti oddílů tak, aby každý oddíl začínal na čísle, které je dělitelné 8 (což pro 512 bytové kousky dá právě velkost 4k) (a byl minimálně stejně velký jako to co potřebujete.) Každopádně pomocí fdisk -l zkontrolovat, že každý oddíl takto začíná a pak jen standardně zapojit do RAIDu.
fdisk -H 224 -S 56 /dev/sdb.
Ano, to vím. Proto se ptám, jak mám potom naložit s tou první partyšnou, kde mám /boot. Ta je na novém disku nyní menší a tím pádem jí do puvodniho raidu nemuzu pridat.
Jinak jak jsem pochopil to, co pise lertimir vyse, mam stejne problem s tim, ze raid je nastripovany na 512B. Takze tzn. ze si nepomuzu a bude porad pomaly, jako bych mel ty oddily nezarovnane?? Hlavni duvod, proc tuhle silenost chci udelat je, ze pole je neskutecne pomale.
mdadm --create /dev/md3 --level 1 --raid-devices=2 missing /dev/sdb2 A nemel by byt ten missing /dev/sda3 ?? Pak si teda ten md3 primountuju, nakopcim na nej data.. a co dal.. jak ho zamenim za ten md0?
>> A nemel by byt ten missing /dev/sda3
pardon A nemel by byt ten missing /dev/sda1
mdadm: You haven't given enough devices (real or missing) to create this array
No jasne.. ale jak mam vytvared dalsi degradovanej raid, kdyz mi to hlasi to, co mi to hlasi?? Ted se snazim zmensit /dev/md0 vc. jeho fs, abych ten disk mohl pridat do raidu /dev/md0.
>> musíte znovu pole vystavět.
To lze udělat na tom běžícím systému, kde mám nyní /dev/md0 a /dev/md1 (nyní v degradovaném režimu)?
>> ještě poznámka, pokud máte stripy pole menší než 4k, tak vám nic nepomůže
To znamena, ze i kdyz zarovnam disk na 4K, vytvorim vetsi oddil a dam do toho meho raidu synchronizovat, rychlost bude porad priserna, jako bych ni nedelal a disk proste synchronizoval na nezarovnanou tabulku oddilu?
[>....................] recovery = 4.6% (67685760/1464894976) finish=943.6min speed=24676K/sec
Poslední stav jsem dal do přílohy.
Jeste bych mel par otazek:
a) je tohle ok na 4K /dev/sdb i v pripde, ze casem vymenim za 4K i /dev/sda?
Sector size (logical/physical): 512 bytes / 4096 bytes
b) je /dev/sdb nyni dobre zarovnany? Prvni sektor je 56, coz je delitelne 8mi a fdisk nehlasi zadne chyby zarovnani
c) az se mi sesynchronizuje md1, mam odebrat stary disk /dev/sda z raidu a nakopirovat na nej rozdeleni oddilu z /dev/sdb? Nebude s tim mit nejaky stary disk zase problem? (pak bych zase sesynchronizoval raid).
To je snad vse,
Diky
PS: omlouvam se vsem za mou debilitu:)
:~# fdisk -lu /dev/sdb Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes 224 heads, 56 sectors/track, 233599 cylinders, total 2930277168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 * 56 464127 232036 fd Linux raid autodetect /dev/sdb2 464128 2930265855 1464900864 fd Linux raid autodetect
fdisk -l /dev/sdc Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 63 heads, 63 sectors/track, 984386 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00006c83 Device Boot Start End Blocks Id System /dev/sdc1 2048 3907029167 1953513560 7 HPFS/NTFS/exFATTedy i když má fyzické 4k sektory, hlásí logické 512B (protože jinak by mu to nechodilo tuším v XP a možná i jinde) a hlásí první sektor od používaného oddílu na čísle 2048. Všechny utility vám zahlásí to číslo které je v MBR. Právě proto, že MSDOS tabulka oddílů má 32bitová pole pro počáteční a koncový sektor, což dá pro poslední byte posledního možného sektoru 2^32*512=2^41=2TiB. Tedy větší než 2TB disk se s použitím MSDOS tabulky nedá používat. Toto omezení řeší GPT.
Tiskni
Sdílej:
