similar to: the Superblock last modify time is in the future after upload a file into the VM

hi,all has anyone set the eflags.TF of vm? I want to introdeuce a VM into single-step by setting the eflags.TF of vm, then I disassemble the bytes at RIP to figure out what''s going on . I have set the trap flag ,but I didn''t achieve what I want. First, I only get hlt,mov, rdtsc, clts, in, out . Second, the VM always crash. does anyone have experience and give

Hello Guys, After upgrade to 1.4.7-1 my FS does not mount anymore. Just after upgrade rpm, FS mount and works fine, but after reboot server, it does not work anymore. FS are created with ocfs2-1.4.4 and ocfs2-tools-1.4.3-1. If I downgrade to old version doesn't work too. Messages when trying to mount with new version: # mount /d01 mount.ocfs2: Device name specified was not found while

I've been trying to use fsck to recover a corrupted filesystem. It appears the original superblock is corrupted too, as it has an inode count of 0. When I start fsck with -b 32760, it uses the alternate superblock and proceeds. However, it restarts from the beginning a couple of times and after the second restart it doesn't use the alternate superblock, stopping instead as it can't

Hello, I had something interesting happen on a RH8 ext3 system I setup.I am at a loss to understand what happened. Info: This system has two IDE disks, partitioned identically, and the largest partition on each (/dev/hda3 and /dev/hdb3, 96GB each) was mirrored in a linux software RAID-1 configuration. It was running fine for many months. Then I updated the kernel and needed to reboot accordingly.

Hi All I just installed a 2 node ,10 r2 rac on centos Linux 4.6 My rac install was done by following Jeff Hunters document (excellent work!) http://www.idevelopment.info/ For storage I used openfiler with the iscsi protocol http://www.openfiler.com/ everything went perfect... to the letter, I gracefully shutdown the 2 nodes , then the openfiler appliance, when I went to start it back up,

Author: jkennedy Repository: /hg/zfs-crypto/gate Revision: 931f9f0e5d2fb0b5da5bc6c0f77c10e668f842cf Log message: 4775289 fsck reports wrong state in superblock if there once has existed a largefile 6302747 Performance regression when deleting large files from a logging ufs filesystem 6362734 df output corrupt after under heavy stress Files: update: usr/src/cmd/fs.d/ufs/fsck/utilities.c update:

Something seems to be wrong with my file systems, and I want to fsck everything. But I cannot. The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, /, swap). OS is up-to-date CentOS 5. So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file systems, and try to run fsck -y /dev/md0 fsck -y /dev/md1 fsck -y /dev/md2 For each try I get an error message:

On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at gmail.com> wrote: > I am reporting this on the advice of the Fedora Users Mailing List Member. > > This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. > > I am reporting this per suggestions made to me on the Fedora Users Mailing List. I would

On 09/20/2014 12:07 AM, Andreas Dilger wrote: > On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008@gmail.com> wrote: >> I am reporting this on the advice of the Fedora Users Mailing List Member. >> >> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. >> >> I am reporting this per

Hi! I'm new to the list. I have a problem with mounting my home directory since my PC crashed. I hope that I can get some help on this list as I don't know much of ext3 myself. The mount command for my /home gives me the following output: # mount /dev/sda6 /mnt/tmp/ mount: wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or other error In some cases useful info

I am reporting this on the advice of the Fedora Users Mailing List Member. This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. I am reporting this per suggestions made to me on the Fedora Users Mailing List. The following is the mailing list exchange: On 09/18/2014 07:01 PM, Robert Nichols wrote: > On

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

Hi, hoping that someone on this list can help me here is the Problem. After a crash it seems the journal could not be recovered. This is what mount gives: root@wuehlkiste:# mount -t ext3 /dev/hdb2 /mnt mount: wrong fs type, bad option, bad superblock on /dev/hdb2, or too many mounted file systems and this is the corresponding logfile-entry: Nov 27 11:16:13 wuehlkiste kernel: attempt to

I have a CentOS-6.8 system which has a suspected HHD failure. I have booted it into rescue mode from a CentOS-6.5 minimal install CD in order to run fsck -c on it. The system hosts several vms. I have activated the lvs associated with these vm using pvscan -s ; vgscan ; vgchange -ay. An lvscan shows the lvs as ACTIVE. None are mounted. When I try to run fsck on any of them I see the

Hi, Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal using the

System info: ------------ [root@angel root]# cat /etc/issue Red Hat Linux release 7.2 (Enigma) Kernel \r on an \m [root@angel root]# uname -a Linux angel 2.4.9-34 #1 Sat Jun 1 06:25:16 EDT 2002 i686 unknown This problem occured after upgrade to kernel 2.4.18-17.7, backed out to previous version now (2.4.9-34). All other system RPMs are up to date according to RHN, and nothing, aside from

Hello list. I have a perfectly working PV host, with this configuration: kernel = "/boot/vmlinuz-2.6.18.8-xen-3.3.0-7mdv" ramdisk = "/boot/initrd-2.6.18.8-xen-3.3.0-7mdv.img" root = "/dev/sda1 ro" extra = "(hd0)/boot/grub/menu.lst" memory = 256 maxmem = 512 name = "sexonthebeach" uuid = "f36962f5-0dec-4708-84a0-f5b4dea48d34" disk = [

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, simple question: how can I execute a "fsck.ocfs2 /dev/sdf"? All I get is - ---snip--- myhost:~ # fsck.ocfs2 /dev/sdf fsck.ocfs2 1.4.3 Checking OCFS2 filesystem in /dev/sdf: Label: SAP01 UUID: 5969C8CABB854F8EA9C17B5B8DE48EC6 Number of blocks: 183500800 Block size: 4096 Number of

hi all, I have a doubt. about event channel of xen, a piece of code here " evtchn_bind_interdomain() { struct domain *ld= current->domain }", it is used to bind domain A and domain B but why it is always current->domain ? -- ---------------------------------------------------------- regards, yandong _______________________________________________ Xen-devel mailing list