I’ve found several manuals describing how to add second disk to Volume Group and transform it into mirror. This does not looks complex, and everyone can do it, when everything is working like described in documentation. The problems start when something goes wrong, and one of steps failed.
\nIn my environment there is virtual machine with CentOS 7 hosted by VMWare ESXi. This VM has system disk on one datastore. To provide redundation on OS level I decided to add second disk with the same capacity from another datastore and create RAID-1 (mirror) on them.
\n
\nCurrent situation looks as follows:<\/p>\n
\r\n[root@prod ~]# lvs\r\n LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert\r\n root centos -wi-ao---- 11.60g\r\n swap centos -wi-ao---- 3.91g\r\n srv data rwi-aor--- 99.99g 100.00\r\n\r\n[root@prod ~]# pvs\r\n PV VG Fmt Attr PSize PFree\r\n \/dev\/sda2 centos lvm2 a-- 15.51g 0\r\n \/dev\/sdb data lvm2 a-- 100.00g 0\r\n \/dev\/sdc data lvm2 a-- 100.00g 0\r\n\r\n[root@prod ~]# pvscan\r\n PV \/dev\/sda2 VG centos lvm2 [15.51 GiB \/ 0 free]\r\n PV \/dev\/sdb VG data lvm2 [100.00 GiB \/ 0 free]\r\n PV \/dev\/sdc VG data lvm2 [100.00 GiB \/ 0 free]\r\n Total: 3 [215.50 GiB] \/ in use: 3 [215.50 GiB] \/ in no VG: 0 [0 ]\r\n\r\n[root@prod ~]# vgscan\r\n Reading all physical volumes. This may take a while...\r\n Found volume group "centos" using metadata type lvm2\r\n Found volume group "data" using metadata type lvm2\r\n<\/pre>\nThere is already VG “centos” created on physical volumene \/dev\/sda2, which contains two logical volumens: root and swap. There is also second VG named “data”, but this one is already mirrored, and we have nothing to do with that. Let’s take a look on \/dev\/sda2 volume:<\/p>\n
\r\n[root@prod ~]# pvdisplay\r\n --- Physical volume ---\r\n PV Name \/dev\/sda2\r\n VG Name centos\r\n PV Size 15.51 GiB \/ not usable 3.00 MiB\r\n Allocatable yes (but full)\r\n PE Size 4.00 MiB\r\n Total PE 3970\r\n Free PE 0\r\n Allocated PE 3970\r\n PV UUID RJaYrc-pV0r-qfNf-S92B-NSJc-mLpF-A5GOkf\r\n<\/pre>\nAs I already wrote, this is VMWare environment, so I created volume with the same capacity on second datastore and I connected it to Virtual Machine with CentOS. Operating system does not know yet about it, so we need to perform bus scan. The simpliest way is to reboot VM, but this requires downtime, and this can be inadvisable. Let’s do it without restart, we need to force bus scan in OS. But at first we take a look what we have:<\/p>\n
\r\n[root@prod ~]# fdisk -l\r\n\r\nDisk \/dev\/sdb: 107.4 GB, 107374182400 bytes, 209715200 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/sdc: 107.4 GB, 107374182400 bytes, 209715200 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/sda: 17.2 GB, 17179869184 bytes, 33554432 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\nDisk label type: dos\r\nDisk identifier: 0x00015ff8\r\n\r\n Device Boot Start End Blocks Id System\r\n\/dev\/sda1 * 2048 1026047 512000 83 Linux\r\n\/dev\/sda2 1026048 33554431 16264192 8e Linux LVM\r\n\r\nDisk \/dev\/mapper\/centos-swap: 4194 MB, 4194304000 bytes, 8192000 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/mapper\/centos-root: 12.5 GB, 12457082880 bytes, 24330240 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/mapper\/data-srv_rmeta_0: 4 MB, 4194304 bytes, 8192 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/mapper\/data-srv_rimage_0: 107.4 GB, 107365793792 bytes, 209698816 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/mapper\/data-srv_rmeta_1: 4 MB, 4194304 bytes, 8192 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/mapper\/data-srv_rimage_1: 107.4 GB, 107365793792 bytes, 209698816 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/mapper\/data-srv: 107.4 GB, 107365793792 bytes, 209698816 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n<\/pre>\nPlease notice additional metadata in mirrored data-srv volume in opposition to centos-root and centos-swap.
\nLet’s scan the bus:<\/p>\n\r\n[root@prod ~]# echo "- - -" > \/sys\/class\/scsi_host\/host0\/scan\r\n[root@prod ~]# echo "- - -" > \/sys\/class\/scsi_host\/host1\/scan\r\n<\/pre>\nIt is good to know to which bus is new disc connected, but there should be no problems when you scan all of them. It is worthwhile to check system logs if anything new appeared.<\/p>\n
\r\n[root@prod ~]# less \/var\/log\/messages\r\n[root@prod ~]# echo "- - -" > \/sys\/class\/scsi_host\/host2\/scan\r\n[root@prod ~]# less \/var\/log\/messages\r\n<\/pre>\nLet’s take a look once more what we have:<\/p>\n
\r\n[root@prod ~]# fdisk -l\r\n\r\nDisk \/dev\/sdb: 107.4 GB, 107374182400 bytes, 209715200 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/sdc: 107.4 GB, 107374182400 bytes, 209715200 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n\r\nDisk \/dev\/sda: 17.2 GB, 17179869184 bytes, 33554432 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\nDisk label type: dos\r\nDisk identifier: 0x00015ff8\r\n\r\n Device Boot Start End Blocks Id System\r\n\/dev\/sda1 * 2048 1026047 512000 83 Linux\r\n\/dev\/sda2 1026048 33554431 16264192 8e Linux LVM\r\n\r\nDisk \/dev\/mapper\/centos-swap: 4194 MB, 4194304000 bytes, 8192000 sectors\r\n[...]\r\n\r\nDisk \/dev\/sdd: 17.2 GB, 17179869184 bytes, 33554432 sectors\r\nUnits = sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\n<\/pre>\nI snipped output, because it looks like before, the only change is that after logical volumes list there is new physical device \/dev\/sdd.
\nNow we need to create the same partition layout like on primary system disk:<\/p>\n\r\n[root@prod ~]# sfdisk -d \/dev\/sda\r\n# partition table of \/dev\/sda\r\nunit: sectors\r\n\r\n\/dev\/sda1 : start= 2048, size= 1024000, Id=83, bootable\r\n\/dev\/sda2 : start= 1026048, size= 32528384, Id=8e\r\n\/dev\/sda3 : start= 0, size= 0, Id= 0\r\n\/dev\/sda4 : start= 0, size= 0, Id= 0\r\n<\/pre>\nAnd this partition layout will be saved to new disk:<\/p>\n
\r\n[root@prod ~]# sfdisk -d \/dev\/sda |sfdisk \/dev\/sdd\r\nChecking that no-one is using this disk right now ...\r\nOK\r\n\r\nDisk \/dev\/sdd: 2088 cylinders, 255 heads, 63 sectors\/track\r\nsfdisk: \/dev\/sdd: unrecognized partition table type\r\n\r\nOld situation:\r\nsfdisk: No partitions found\r\n\r\nNew situation:\r\nUnits: sectors of 512 bytes, counting from 0\r\n\r\n Device Boot Start End #sectors Id System\r\n\/dev\/sdd1 * 2048 1026047 1024000 83 Linux\r\n\/dev\/sdd2 1026048 33554431 32528384 8e Linux LVM\r\n\/dev\/sdd3 0 - 0 0 Empty\r\n\/dev\/sdd4 0 - 0 0 Empty\r\nWarning: partition 1 does not end at a cylinder boundary\r\nWarning: partition 2 does not start at a cylinder boundary\r\nWarning: partition 2 does not end at a cylinder boundary\r\nSuccessfully wrote the new partition table\r\n\r\nRe-reading the partition table ...\r\n\r\nIf you created or changed a DOS partition, \/dev\/foo7, say, then use dd(1)\r\nto zero the first 512 bytes: dd if=\/dev\/zero of=\/dev\/foo7 bs=512 count=1\r\n(See fdisk(8).)\r\n<\/pre>\nLet’s take a look how it looks now on \/dev\/sdd:<\/p>\n
\r\n[root@prod ~]# sfdisk -d \/dev\/sdd\r\n# partition table of \/dev\/sdd\r\nunit: sectors\r\n\r\n\/dev\/sdd1 : start= 2048, size= 1024000, Id=83, bootable\r\n\/dev\/sdd2 : start= 1026048, size= 32528384, Id=8e\r\n\/dev\/sdd3 : start= 0, size= 0, Id= 0\r\n\/dev\/sdd4 : start= 0, size= 0, Id= 0\r\n<\/pre>\nLooks good, let’s create phisycal volume:<\/p>\n
\r\n[root@prod ~]# pvcreate \/dev\/sdd2\r\n Physical volume "\/dev\/sdd2" successfully created\r\n\r\n[root@prod ~]# pvs\r\n PV VG Fmt Attr PSize PFree\r\n \/dev\/sda2 centos lvm2 a-- 15.51g 0\r\n \/dev\/sdb data lvm2 a-- 100.00g 0\r\n \/dev\/sdc data lvm2 a-- 100.00g 0\r\n \/dev\/sdd2 lvm2 a-- 15.51g 15.51g\r\n<\/pre>\nAnd expand “centos” Volume Group:<\/p>\n
\r\n[root@prod ~]# vgextend centos \/dev\/sdd2\r\n Volume group "centos" successfully extended\r\n\r\n[root@prod ~]# pvs\r\n PV VG Fmt Attr PSize PFree\r\n \/dev\/sda2 centos lvm2 a-- 15.51g 0\r\n \/dev\/sdb data lvm2 a-- 100.00g 0\r\n \/dev\/sdc data lvm2 a-- 100.00g 0\r\n \/dev\/sdd2 centos lvm2 a-- 15.51g 15.51g\r\n<\/pre>\nDone, now transform it into mirror:<\/p>\n
\r\n[root@prod ~]# lvconvert -m 1 --corelog centos\/root\r\n Insufficient free space: 1 extents needed, but only 0 available\r\n[root@prod ~]# lvconvert -m 1 --alloc anywhere centos\/root\r\n Insufficient free space: 1 extents needed, but only 0 available\r\n<\/pre>\nOoops… <\/p>\n
And here all of mentioned at beginning manuals becomes useless. Those which I found didn’t predict this situation or didn’t provide resolution for this. There was some tries with allocation of space for metadata in different places or shrinking partition, but it ended without success or total disaster with data consistency. During my research I didn’t found the solution which I applied, that’s why I’m describing this. I decided to switch off swap space and reduce swap partition, to provide some space for metadata. Let’s begin from checking:<\/p>\n
\r\n[root@prod ~]# swapon\r\nNAME TYPE SIZE USED PRIO\r\n\/dev\/dm-0 partition 3.9G 0B -1\r\n<\/pre>\nLet’s switch off swap space (if there is only one, we can use -a):<\/p>\n
\r\n[root@prod ~]# swapoff -av\r\nswapoff \/dev\/dm-0\r\n<\/pre>\nLet’s check again:<\/p>\n
\r\n[root@prod ~]# swapon\r\n<\/pre>\nNow it’s time to reduce logical volume (here is my mistake, where I put “512M” instead of “-512M”, and volume was reduced to 512M, so remember about minus sign):<\/p>\n
\r\n[root@prod ~]# lvreduce centos\/swap -L 512M\r\n WARNING: Reducing active logical volume to 512.00 MiB\r\n THIS MAY DESTROY YOUR DATA (filesystem etc.)\r\nDo you really want to reduce swap? [y\/n]: y\r\n Reducing logical volume swap to 512.00 MiB\r\n Logical volume swap successfully resized\r\n<\/pre>\nLet’s check:<\/p>\n
\r\n[root@prod ~]# lvs\r\n LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert\r\n root centos -wi-ao---- 11.60g\r\n swap centos -wi-a----- 512.00m\r\n srv data rwi-aor--- 99.99g 100.00\r\n<\/pre>\nSome space are freed, so let’s try to transform root filesystem into mirrored fs:<\/p>\n
\r\n[root@prod ~]# lvconvert -m 1 centos\/root\r\n[root@prod ~]# lvs\r\n LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert\r\n root centos rwi-aor--- 11.60g 0.00\r\n swap centos -wi-a----- 512.00m\r\n srv data rwi-aor--- 99.99g 100.00\r\n<\/pre>\nVoila! Operation completed successfully, let’s do the same with swap:<\/p>\n
\r\n[root@prod ~]# lvconvert -m 1 centos\/swap\r\n<\/pre>\nAnd check:<\/p>\n
\r\n[root@prod ~]# lvs\r\n LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert\r\n root centos rwi-aor--- 11.60g 55.66\r\n swap centos rwi-a-r--- 512.00m 100.00\r\n srv data rwi-aor--- 99.99g 100.00\r\n<\/pre>\nMirrors are done, root filesystem is syncing, but we can expand swap to maximal available capacity:<\/p>\n
\r\n[root@prod ~]# lvextend -l 100%FREE centos\/swap\r\n Extending 2 mirror images.\r\n Extending logical volume swap to 6.80 GiB\r\n device-mapper: resume ioctl on failed: Invalid argument\r\n Unable to resume centos-swap (253:0)\r\n Problem reactivating swap\r\n libdevmapper exiting with 1 device(s) still suspended.\r\n<\/pre>\nUnfortunatelly system didn’t activate swap automatically, because swap signature was destroyed and needs to be restored:<\/p>\n
\r\n[root@prod ~]# mkswap \/dev\/centos\/swap\r\n<\/pre>\nNow we can activate swap in system:<\/p>\n
\r\n[root@prod ~]# swapon -av\r\nswapon \/dev\/mapper\/centos-swap\r\nswapon: \/dev\/mapper\/centos-swap: found swap signature: version 1, page-size 4, same byte order\r\nswapon: \/dev\/mapper\/centos-swap: pagesize=4096, swapsize=4185915392, devsize=4185915392\r\n<\/pre>\nLet’s check if it works:<\/p>\n
\r\n[root@prod ~]# swapon\r\nNAME TYPE SIZE USED PRIO\r\n\/dev\/dm-4 partition 3.9G 0B -1\r\n<\/pre>\nThis way I went a crash course of LVM logic, because I didn’t have opportunity to manage LVM before. I hope this manual will help those which encountered similar problem.<\/p>","protected":false},"excerpt":{"rendered":"
Sorry, this entry is only available in Polish. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.Sprawa niby...<\/p>\n","protected":false},"author":1,"featured_media":653,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_newsletter_tier_id":0,"footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[98],"tags":[99,100],"jetpack_publicize_connections":[],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/drfugazi.eu.org\/wp-content\/uploads\/2015\/07\/cropped-google-datacenter-1.jpg?fit=1260%2C240&ssl=1","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p7M9Tz-6d","jetpack-related-posts":[{"id":381,"url":"https:\/\/drfugazi.eu.org\/en\/rootowanie-samsunga-galaxy-s-advance-gt-i9070\/","url_meta":{"origin":385,"position":0},"title":"Rootowanie Samsunga Galaxy S Advance (GT-I9070)","author":"drfugazi","date":"Monday November 11th, 2013","format":false,"excerpt":"Sorry, this entry is only available in Polish. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.Kupuj\u0105c Samsunga Galaxy S Advance spodziewa\u0142em si\u0119 nieco lepszej wydajno\u015bci. Jeszcze z fabrycznie wgranym systemem Android 2.3.6 Gingerbread\u2026","rel":"","context":"In "Android"","block_context":{"text":"Android","link":"https:\/\/drfugazi.eu.org\/en\/category\/android\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":187,"url":"https:\/\/drfugazi.eu.org\/en\/","url_meta":{"origin":385,"position":1},"title":"Funambol – pierwsze uruchomienie","author":"drfugazi","date":"Thursday June 10th, 2010","format":false,"excerpt":"OK. Zak\u0142adam, \u017ce mamy zainstalowany serwer Funambol, tak jak opisa\u0142em tutaj. Nadszed\u0142 czas na uruchomienie serwera. Prosz\u0119 wej\u015b\u0107 do katalogu Funambol (domy\u015blnie: \/opt\/Funambol) i wykonaj polecenie: # .\/bin\/funambol start je\u015bli masz szcz\u0119\u015bcie to serwer wystartuje, ale na Solarisie trzeba zmodyfikowa\u0107 skrypty startowe, gdy\u017c prawdopodobnie zobaczysz taki komunikat: .\/bin\/funambol: J2EE_HOME=\/opt\/Funambol\/tools\/tomcat: is\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":324,"url":"https:\/\/drfugazi.eu.org\/en\/funambol-pierwsze-uruchomienie\/","url_meta":{"origin":385,"position":2},"title":"Funambol – pierwsze uruchomienie","author":"","date":"Thursday June 10th, 2010","format":false,"excerpt":"OK. Zak\u0142adam, \u017ce mamy zainstalowany serwer Funambol, tak jak opisa\u0142em tutaj. Nadszed\u0142 czas na uruchomienie serwera. Prosz\u0119 wej\u015b\u0107 do katalogu Funambol (domy\u015blnie: \/opt\/Funambol) i wykonaj polecenie: # .\/bin\/funambol start je\u015bli masz szcz\u0119\u015bcie to serwer wystartuje, ale na Solarisie trzeba zmodyfikowa\u0107 skrypty startowe, gdy\u017c prawdopodobnie zobaczysz taki komunikat: .\/bin\/funambol: J2EE_HOME=\/opt\/Funambol\/tools\/tomcat: is\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":356,"url":"https:\/\/drfugazi.eu.org\/en\/postfix-2\/","url_meta":{"origin":385,"position":3},"title":"Postfix","author":"drfugazi","date":"Friday June 29th, 2012","format":false,"excerpt":"Postfix is Wietse Venema's mail server that started life at IBM research as an alternative to the widely-used Sendmail program. Postfix attempts to be fast, easy to administer, and secure. The outside has a definite Sendmail-ish flavor, but the inside is completely different. Built from source code, Postfix can run\u2026","rel":"","context":"In "Mail system"","block_context":{"text":"Mail system","link":"https:\/\/drfugazi.eu.org\/en\/category\/mail-system\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":303,"url":"https:\/\/drfugazi.eu.org\/en\/minicm7-x10-mini-pro-rootowanie\/","url_meta":{"origin":385,"position":4},"title":"MiniCM7 dla X10 Mini Pro – rootowanie i xRecovery","author":"drfugazi","date":"Wednesday August 10th, 2011","format":false,"excerpt":"W poprzednim artykule pisa\u0142em o przygotowaniu X10 Mini Pro do instalacji nowego firmware (ROMu). Zako\u0144czy\u0142em tamten wpis na przywr\u00f3ceniu\/aktualizacji systemu Android do odpowiedniej wersji, tak aby mo\u017cna by\u0142o przeprowadzi\u0107 upgrade. Prosz\u0119 pami\u0119ta\u0107, \u017ce nie ponosz\u0119 odpowiedzialno\u015bci za ewentualne uszkodzenia sprz\u0119tu b\u0105d\u017a oprogramowania ani utrat\u0119 jakichkolwiek danych, oraz \u017ce instalowany ROM\u2026","rel":"","context":"In "Android"","block_context":{"text":"Android","link":"https:\/\/drfugazi.eu.org\/en\/category\/android\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":379,"url":"https:\/\/drfugazi.eu.org\/en\/jelly-bean-dla-sony-ericsson-xperia-ray\/","url_meta":{"origin":385,"position":5},"title":"(Polski) Jelly Bean dla Sony Ericsson Xperia Ray","author":"drfugazi","date":"Sunday November 3rd, 2013","format":false,"excerpt":"Sorry, this entry is only available in Polish. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.Sony Ericsson Xperia Ray (ST18i) dostarczany by\u0142 z systemem Google Android w wersji 2.3 (Gingerbread). Po jakim\u015b czasie\u2026","rel":"","context":"In "Android"","block_context":{"text":"Android","link":"https:\/\/drfugazi.eu.org\/en\/category\/android\/"},"img":{"alt_text":"Xperia Ray Jelly Bean","src":"https:\/\/i0.wp.com\/drfugazi.eu.org\/wp-content\/uploads\/2013\/11\/screenshot_ray_en.jpg?fit=480%2C854&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/posts\/385"}],"collection":[{"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/comments?post=385"}],"version-history":[{"count":6,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/posts\/385\/revisions"}],"predecessor-version":[{"id":447,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/posts\/385\/revisions\/447"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/media\/653"}],"wp:attachment":[{"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/media?parent=385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/categories?post=385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/tags?post=385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}