pepino:~/XFCE4/xfce-4.0.0/src/xfce-utils-4.0.0 # updatedb /usr/bin/find: /root/oldetc/etc/skel/.seyon/script.unix: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/script.unix: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/script.unix: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/script.unix: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/script.unix: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/script.unix: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/startup: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/startup: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/startup: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/startup: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/startup: Input/output error /usr/bin/find: /root/oldetc/etc/skel/.seyon/startup: Input/output error /usr/bin/find: /root/oldetc/etc/usbmgr/vendor/04c1: Input/output error /usr/bin/find: /root/oldetc/etc/usbmgr/vendor/04a5/2040: Input/output error /usr/bin/find: /root/oldetc/etc/usbmgr/vendor/05da: Input/output error /usr/bin/find: /root/oldetc/etc/usbmgr/vendor/07aa: Input/output error /usr/bin/find: /root/oldetc/etc/usbmgr/vendor/07b8/4002: Input/output error /usr/bin/find: /root/oldetc/etc/usbmgr/class/e0/01/01: Input/output error /usr/bin/find: /root/oldetc/etc/webmin/dhcpd: Input/output error /usr/bin/find: /root/oldetc/etc/webmin/mount: Input/output error /usr/bin/find: /root/oldetc/etc/webmin/status/services: Input/output error
On 26 Sep 2003 10:23:51 -0400 landy <landy@despiertapr.com> wrote:
/usr/bin/find: /root/oldetc/etc/skel/.seyon/script.unix: Input/output error
Looks like it. Time to run badblocks. Charles -- "I once witnessed a long-winded, month-long flamewar over the use of mice vs. trackballs...It was very silly." (By Matt Welsh)
I tried badblocks and got some weird output, then realised it handles only ext2 filesystems (man badblocks), no good for reiserfs etc., don't know about ext3. man reiserfsck ------ --check This default action checks file system consistency and reports but does not repair any corruption that it finds. This option may be used on a read-only file system mount. The --check option exits with status 0 to indicate that no corruption was found. Otherwise, reiserfsck returns 1 to indicate corruption that can be fixed with --fix-fixable and 2 to indicate corruption that requires --rebuild-tree. --fix-fixable This option recovers certain kinds of corruption that do not require rebuilding the entire file system tree (--rebuild-tree). Normally you only need this option if the --check option reports "corruption that can be fixed with --fix- fixable". This includes: zeroing invalid data-block pointers, correcting st_size and st_blocks for directories, and deleting invalid directory entries. Regards Sid. Charles Philip Chan wrote:
On 26 Sep 2003 10:23:51 -0400 landy <landy@despiertapr.com> wrote:
/usr/bin/find: /root/oldetc/etc/skel/.seyon/script.unix: Input/output error
Looks like it. Time to run badblocks.
Charles
On Sat, 27 Sep 2003 15:29:44 +0100 Sid Boyce <sboyce@blueyonder.co.uk> wrote:
I tried badblocks and got some weird output, then realised it handles only ext2 filesystems (man badblocks), no good for reiserfs etc., don't know about ext3.
This is why I am using ext3 and not Reiserfs yet- the rescue tools are not mature enough (with ext2/3, one can pass the -c option in e2fsck for badblocks). Badblocks handling in Reiserfs is rather convoluted at this point. Instructions are here: http://www.namesys.com/bad-block-handling.html Charles -- "Oh, I've seen copies [of Linux Journal] around the terminal room at The Labs." (By Dennis Ritchie)
participants (3)
-
Charles Philip Chan -
landy -
Sid Boyce