filesystem: recover or not to recover?
 

Hi all,

After a power loss the backup server complains with the following after starting an rsync script:

<clip from stdout>
[root@bkupsrv pub]# building file list ...
Gtk-CRITICAL **: file gtkcombo.c: line 849 (gtk_combo_set_popdown_strings): assertion `strings != NULL' failed.

Gtk-CRITICAL **: file gtkcombo.c: line 849 (gtk_combo_set_popdown_strings): assertion `strings != NULL' failed.
Gdk-ERROR **: BadMatch (invalid parameter attributes)
serial 45056 error_code 8 request_code 70 minor_code 0
Gdk-ERROR **: BadMatch (invalid parameter attributes)
serial 45057 error_code 8 request_code 67 minor_code 0
done
</clip from stdout>

I've always had bad luck rebuilding filesystems in windoze so have never let linux try at startup. it's ext3 so i'm tempted to see what it does, but wonder if anybody recognizes this first or if it's recommended/not recommended to let filesystem repair do its thing at startup. The alternative is to re-load the ghost image of the server drive.

Thanks if any input, - bp

Re: filesystem: recover or not to recover?
 

The lines from stdout contains not anything about filesystems.
Next rebuilding filesystems -what do you mean?
Do you mean something like fsck after system crashes or power fails
You have to do that through fstab
man fstab

Hi rch, thx for the reply.

The stdout comes from a backup server that worked perfectly for >1 year. Every day it ran an rsync script that syncs/backs up data from several boxes via smbfs and nfs without ever having any issues. Now that the power went out (UPS eventually gave out and the box died from power loss) the rsync script complains with the output I listed above. I concluded the problem resulted from a filesystem error since it offered to check filesystems when i rebooted (fsck). However, I don't have experience checking filesystems in linux so didn't opt to let it try as I don't know if it'll just make it worse or possibly better. I am unsure of how to interpret Gtk-CRITICAL errors when I run rsync but recent testing shows it's still doing its job. I'll probably re-load the ghost image of the server as I expect that will make rsync run without Gtk complaining since it worked fine before crashing. I was wondering what the error is, and perhaps if people have good or bad luck using fsck to actually *fix* a corrupted ext3 filesystem.

thx, -bp

The Gtk and Gdk are for your gnome applications using gimp tool kit or gimp drawing kit.I think that you can safely fsck your partition .If some files get corrupted(very less likely) you can still retrieve them through /lost+found.Remember that ext3 is many times reliable and safe as compared to fat32.