search for: 2099200

...te_request: I/O error, dev vda, sector 23125016 [ 483.898034] blk_update_request: I/O error, dev vda, sector 2161832 [ 483.901103] blk_update_request: I/O error, dev vda, sector 2161832 [ 483.904045] Aborting journal on device vda1-8. [ 483.906959] blk_update_request: I/O error, dev vda, sector 2099200 [ 483.908306] blk_update_request: I/O error, dev vda, sector 2099200 [ 483.909585] Buffer I/O error on dev vda1, logical block 262144, lost sync page write [ 483.911121] blk_update_request: I/O error, dev vda, sector 2048 [ 483.912192] blk_update_request: I/O error, dev vda, sector 2048 [ 483....

FYI I set up replica 3 (no arbiter this time), did the same thing - rebooted one node during lots of file IO on VM and IO stopped. As I mentioned either here or in another thread, this behavior is caused by high default of network.ping-timeout. My main problem used to be that setting it to low values like 3s or even 2s did not prevent the FS to be mounted as read-only in the past (at least with

...; I/O size (minimum/optimal): 512 bytes / 512 bytes >> Disk label type: dos >> Disk identifier: 0x0000c89d >> >> Device Boot Start End Blocks Id System >> /dev/sda1 2048 2099199 1048576 83 Linux >> /dev/sda2 2099200 4196351 1048576 82 Linux swap / >> Solaris >> /dev/sda3 4196352 468862127 232332888 83 Linux >> > > LBA 17066160 would be on sda3. > > dd if=/dev/sda skip=17066160 count=1 2>/dev/null | hexdump -C > > That'll read that sector a...

...s Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0000c89d Device Boot Start End Blocks Id System /dev/sda1 2048 2099199 1048576 83 Linux /dev/sda2 2099200 4196351 1048576 82 Linux swap / Solaris /dev/sda3 4196352 468862127 232332888 83 Linux But I don't know where it is in relation to the way the drive was formatted in my notebook. I think it would have been in the / partition. > And what do you get for > smar...

...s there as it shows 16GB. The original disk had 10GB. [root ~]# fdisk -l /dev/xvda Disk /dev/xvda: 16.1 GB, 16106127360 bytes, 31457280 sectors [snip] Device Boot Start End Blocks Id System /dev/xvda1 * 2048 2099199 1048576 83 Linux /dev/xvda2 2099200 20971519 9436160 8e Linux LVM vgs also shows 0 Free PE: [root at CTSSVN01 ~]# vgs VG #PV #LV #SN Attr VSize VFree cl_vm731611 1 2 0 wz--n- 9.00g 0 Thanks, On Wed, Feb 22, 2017 at 8:06 AM, Jon LaBadie <jcu at labadie.us> wrote: > On Wed, Feb 22, 2017...

...* (hd[disk number],[partition number])/path/to/file > * > * E.G.: (hd0,1)/dir/file means /dir/file at partition 1 of the disk 0. > * Disk and Partition numbering starts from 0 and 1 respectivelly. > */ > ... > > > # fdisk -l /dev/vdb | grep -w 83 > /dev/vdb2 2099200 4194303 2095104 1023M 83 Linux > # mount | grep vdb2 > /dev/vdb2 on /data type ext4 ... > # ls -1 /data > initramfs-4.4.0-0.rc5.git0.1.fc24.x86_64.img > lost+found > vmlinuz-4.4.0-0.rc5.git0.1.fc24.x86_64 > > > BOOT: > find_all_partitions: failed to set EFI disk info...

...t ~]# fdisk -l /dev/xvda > > > > Disk /dev/xvda: 16.1 GB, 16106127360 bytes, 31457280 sectors [snip] > > > > Device Boot Start End Blocks Id System > > /dev/xvda1 * 2048 2099199 1048576 83 Linux > > /dev/xvda2 2099200 20971519 9436160 8e Linux LVM > > > > > > vgs also shows 0 Free PE: > > [root at CTSSVN01 ~]# vgs > > VG #PV #LV #SN Attr VSize VFree > > cl_vm731611 1 2 0 wz--n- 9.00g 0 > > > > > > Thanks, > > > >...

...h=multifs-for-upstream#n27 * MULTIFS SYNTAX: * (hd[disk number],[partition number])/path/to/file * * E.G.: (hd0,1)/dir/file means /dir/file at partition 1 of the disk 0. * Disk and Partition numbering starts from 0 and 1 respectivelly. */ ... # fdisk -l /dev/vdb | grep -w 83 /dev/vdb2 2099200 4194303 2095104 1023M 83 Linux # mount | grep vdb2 /dev/vdb2 on /data type ext4 ... # ls -1 /data initramfs-4.4.0-0.rc5.git0.1.fc24.x86_64.img lost+found vmlinuz-4.4.0-0.rc5.git0.1.fc24.x86_64 BOOT: find_all_partitions: failed to set EFI disk info efi_multifs_init: failed to find disk partitions:...

...mal): 512 bytes / 512 bytes >>> Disk label type: dos >>> Disk identifier: 0x0000c89d >>> >>> Device Boot Start End Blocks Id System >>> /dev/sda1 2048 2099199 1048576 83 Linux >>> /dev/sda2 2099200 4196351 1048576 82 Linux swap / >>> Solaris >>> /dev/sda3 4196352 468862127 232332888 83 Linux >>> >> >> LBA 17066160 would be on sda3. >> >> dd if=/dev/sda skip=17066160 count=1 2>/dev/null | hexdump -C >> >&g...

...nal disk had 10GB. > [root ~]# fdisk -l /dev/xvda > > Disk /dev/xvda: 16.1 GB, 16106127360 bytes, 31457280 sectors [snip] > > Device Boot Start End Blocks Id System > /dev/xvda1 * 2048 2099199 1048576 83 Linux > /dev/xvda2 2099200 20971519 9436160 8e Linux LVM > > > vgs also shows 0 Free PE: > [root at CTSSVN01 ~]# vgs > VG #PV #LV #SN Attr VSize VFree > cl_vm731611 1 2 0 wz--n- 9.00g 0 > > > Thanks, > > > On Wed, Feb 22, 2017 at 8:06 AM, Jon LaBadie...

...512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk label type: dos > Disk identifier: 0x0000c89d > > Device Boot Start End Blocks Id System > /dev/sda1 2048 2099199 1048576 83 Linux > /dev/sda2 2099200 4196351 1048576 82 Linux swap / > Solaris > /dev/sda3 4196352 468862127 232332888 83 Linux > LBA 17066160 would be on sda3. dd if=/dev/sda skip=17066160 count=1 2>/dev/null | hexdump -C That'll read that sector and display hex and ascii. If you recognize...

Hello, I have a CentOS VM with only one disk on a Xenserver. The disk has 2 partitions: /dev/xvda1 -> /boot /dev/xvda2 -> a physical volume for LVM I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I just have to do "pvresize /dev/xvda" to have the additional space added to the disk. But for some reason it does not work for this disk. [root ~]# pvresize

...es >>>> Disk label type: dos >>>> Disk identifier: 0x0000c89d >>>> >>>> Device Boot Start End Blocks Id System >>>> /dev/sda1 2048 2099199 1048576 83 Linux >>>> /dev/sda2 2099200 4196351 1048576 82 Linux swap / >>>> Solaris >>>> /dev/sda3 4196352 468862127 232332888 83 Linux >>>> >>> >>> LBA 17066160 would be on sda3. >>> >>> dd if=/dev/sda skip=17066160 count=1 2>/dev/null...

...r, dev vda, sector 23125016 > [ 483.898034] blk_update_request: I/O error, dev vda, sector 2161832 > [ 483.901103] blk_update_request: I/O error, dev vda, sector 2161832 > [ 483.904045] Aborting journal on device vda1-8. > [ 483.906959] blk_update_request: I/O error, dev vda, sector 2099200 > [ 483.908306] blk_update_request: I/O error, dev vda, sector 2099200 > [ 483.909585] Buffer I/O error on dev vda1, logical block 262144, > lost sync page write > [ 483.911121] blk_update_request: I/O error, dev vda, sector 2048 > [ 483.912192] blk_update_request: I/O error, dev...

I am building a new system using an Kingston 240GB SSD drive I pulled from my notebook (when I had to upgrade to a 500GB SSD drive). Centos install went fine and ran for a couple days then got errors on the console. Here is an example: [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10)

...or 23125016 >> [ 483.898034] blk_update_request: I/O error, dev vda, sector 2161832 >> [ 483.901103] blk_update_request: I/O error, dev vda, sector 2161832 >> [ 483.904045] Aborting journal on device vda1-8. >> [ 483.906959] blk_update_request: I/O error, dev vda, sector 2099200 >> [ 483.908306] blk_update_request: I/O error, dev vda, sector 2099200 >> [ 483.909585] Buffer I/O error on dev vda1, logical block 262144, >> lost sync page write >> [ 483.911121] blk_update_request: I/O error, dev vda, sector 2048 >> [ 483.912192] blk_update_req...

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not