X-Git-Url: http://git.rot13.org/?p=gnt-info;a=blobdiff_plain;f=doc%2Fdeboostrap-4k-msdos.txt;h=151dd2051f630bdf1fab5abe4edff7b2ad081245;hp=292e550d8a1ed0a82213402bd52c15f85a60e8e8;hb=ec38745107c7c573f36e3bfd7ca67831132e4795;hpb=97dfb198b7967834b916ba9291563942e5314bc7

diff --git a/doc/deboostrap-4k-msdos.txt b/doc/deboostrap-4k-msdos.txt
index 292e550..151dd20 100644
--- a/doc/deboostrap-4k-msdos.txt
+++ b/doc/deboostrap-4k-msdos.txt
@@ -1,3 +1,19 @@
+This is working configuration:
+
++ ssh r1u28.gnt.ffzg.hr fdisk -l /var/run/ganeti/instance-disks/armbian:0
+Disk /var/run/ganeti/instance-disks/armbian:0: 40 GiB, 42949672960 bytes, 10485760 sectors
+Units: sectors of 1 * 4096 = 4096 bytes
+Sector size (logical/physical): 4096 bytes / 4096 bytes
+I/O size (minimum/optimal): 4096 bytes / 4096 bytes
+Disklabel type: dos
+Disk identifier: 0xa25190c0
+
+Device                                     Boot Start      End  Sectors  Size Id Type
+/var/run/ganeti/instance-disks/armbian:0p1 *     2048 83886079 83884032  320G 83 Linux
+
+confused yet? Why is partition size 320G when disk is only 40G?
+
+
 This is a story about booting ganeti instances from kernel inside virtual machine.
 We are using ganeti-instance-debootstrap to create instances and have disk with 4k
 blocks: