Will that help flush the data, Yes it will, it doesn't matter who does the fsync. Note that you likely want to fsync the directory that the file resides in too, in order to sync the metadata of the file....

Have you checked any potential opcode caches and their settings? In the past I have had some issues there, eg not detecting changed files. Specifically, this situation can and will happen if opcache.use_cwd setting is set to zero. opcache.use_cwd boolean If enabled, OPcache appends the current working directory to the...

This is a complex issue. The only way that is 100% effective is physical destruction. The problem is that the drive firmware can mark sectors as bad and remap them to a pool of spares. These sectors are effectively no longer accessible to you but the old data may be...

McAfee VSE for linux 1.9 is not officially supported for RHEL 6.5. dmesg shows: linuxshield module is older than RHEL 6.2 ... applying fixups The McAfee 'linuxshield' kernel module is causing this issue. Curiously, it cannot be unloaded with modprobe, because attempting to do so results in modprobe being unable...

Eventually found the answer online... Boot from LiveCD Open a terminal sudo su -l Switch user to root vgchange -aay This is the magic. It will automatically find and activate existing volume groups. e2fsck -f /dev/mapper/VolGroup-lv_root Force check the volume for errors resize2fs /dev/mapper/VolGroup-lv_root Add available space to volume e2fsck...

I have got this fixed by doing as I mentioned above. As per dumpe2fs o/p I had below for group 0: Group 0: (Blocks 0-32767) Checksum 0x8bba, unused inodes 8069 Primary superblock at 0, Group descriptors at 1-1 Reserved GDT blocks at 2-474 Block bitmap at 475 (+475), Inode bitmap...

sudo mount -t ext4 /dev/sdb/ /media/backup/ is wrong in 2 aspects: the trailing / after sdb is wrong: /dev/sdb is not a directory, but a device node. sdb itself is wrong as it refers to the whole device, not to the partiotion with the file system. Do sudo mount -t...

Not sure if I should be posting this... To be run as root: # note: very dangerous thing to do: dd if=/dev/urandom of=/dev/sda3 bs=1M where sda3 is the partition you need to "crash". cat /proc/mounts or df or fdisk -l can tell you which device you are looking for....