-----Original Message----- From: David Teigland [mailto:teigland@xxxxxxxxxx] Sent: den 26 september 2007 17:52 To: Borgström Jonas Cc: linux-cluster@xxxxxxxxxx Subject: Re: Found unlinked inode > On Wed, Sep 26, 2007 at 05:40:59PM +0200, Borgstr??m Jonas wrote: > > Hi again, > > > > I was just able to reproduce the filesystem corruption again. This time > > four lost zero-sized inodes were found :( And unfortunately > > mounting+umounting the filesystem didn't make the lost inodes go away. > > I still have a copy of the corrupted filesystem if there is any more > > things you want me to test. > > I still think this is probably expected and cleaned up properly by gfs. > When you mount you should see something like this: > > GFS: fsid=bull:x.2: jid=2: Trying to acquire journal lock... > GFS: fsid=bull:x.2: jid=2: Looking at journal... > GFS: fsid=bull:x.2: jid=2: Done > GFS: fsid=bull:x.2: Scanning for log elements... > GFS: fsid=bull:x.2: Found 48 unlinked inodes > GFS: fsid=bull:x.2: Found quota changes for 0 IDs > GFS: fsid=bull:x.2: Done > > It suspect the unlinked inodes found by fsck are the same as those gfs > finds in the journal when mounting. Note that a cleanly shut down journal > may still have records of unlinked inodes that need to be deallocated. > This is what I get when mounting the filesystem: Trying to join cluster "lock_dlm", "test-db:pg_fs" Joined cluster. Now mounting FS... GFS: fsid=test-db:pg_fs.0: jid=0: Trying to acquire journal lock... GFS: fsid=test-db:pg_fs.0: jid=0: Looking at journal... GFS: fsid=test-db:pg_fs.0: jid=0: Done GFS: fsid=test-db:pg_fs.0: jid=1: Trying to acquire journal lock... GFS: fsid=test-db:pg_fs.0: jid=1: Looking at journal... GFS: fsid=test-db:pg_fs.0: jid=1: Done > You may need to mount/unmount all of the journals (so all journals are > replayed). something like > It doesn't appear to make any difference: mount /dev/testdb/pg_fs /var/lib/pgsql -o lockproto=lock_nolock,hostdata=jid=0 Trying to join cluster "lock_nolock", "test-db:pg_fs" Lock_Nolock (built Jul 10 2007 06:40:22) installed Joined cluster. Now mounting FS... GFS: fsid=test-db:pg_fs.0: jid=0: Trying to acquire journal lock... GFS: fsid=test-db:pg_fs.0: jid=0: Looking at journal... GFS: fsid=test-db:pg_fs.0: jid=0: Done GFS: fsid=test-db:pg_fs.0: jid=1: Trying to acquire journal lock... GFS: fsid=test-db:pg_fs.0: jid=1: Looking at journal... GFS: fsid=test-db:pg_fs.0: jid=1: Done mount /dev/testdb/pg_fs /var/lib/pgsql -o lockproto=lock_nolock,hostdata=jid=1 Trying to join cluster "lock_nolock", "test-db:pg_fs" Joined cluster. Now mounting FS... GFS: fsid=test-db:pg_fs.0: jid=0: Trying to acquire journal lock... GFS: fsid=test-db:pg_fs.0: jid=0: Looking at journal... GFS: fsid=test-db:pg_fs.0: jid=0: Done GFS: fsid=test-db:pg_fs.0: jid=1: Trying to acquire journal lock... GFS: fsid=test-db:pg_fs.0: jid=1: Looking at journal... GFS: fsid=test-db:pg_fs.0: jid=1: Done And running gfs_fsck at this points yields the same errors as before. Regards, Jonas -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
