fsck cannot determine which of the two inodes is incorrect. In such cases,
fsck makes a copy of one of the inodes (with data) and asks the user to
delete the bad file after mounting.
On Sun, Mar 23, 2014 at 7:18 AM, Eric Raskin eras...@paslists.com wrote:
I did some more research by running a
Thanks. We will make time for it to run.
On Mar 24, 2014 7:14 PM, Sunil Mushran sunil.mush...@gmail.com wrote:
fsck cannot determine which of the two inodes is incorrect. In such cases,
fsck makes a copy of one of the inodes (with data) and asks the user to
delete the bad file after mounting.
I did some more research by running a fsck -fn. Basically it is one
inode that is wrong and needs to be cleared. Is there a way to do that
via debugfs? If I can delete that one inode, then all the doubly-linked
clusters will not be doubly linked any more and all of the errors will
go away.
Hi:
I am running a two-node Oracle VM Server 2.2.2 installation. We were
having some strange problems creating new virtual machines, so I shut
down the systems and unmounted the OVS Repository (ocfs2 file system on
Equallogic equipment).
I ran a fsck -y first, which replayed the logs and said
Cloning the inode means inode + data. Let it finish.
On Sat, Mar 22, 2014 at 3:44 PM, Eric Raskin eras...@paslists.com wrote:
Hi:
I am running a two-node Oracle VM Server 2.2.2 installation. We were
having some strange problems creating new virtual machines, so I shut down
the systems
