From: Oleg Drokin <green@namesys.com>
To: Bernd Schubert <bernd-schubert@web.de>
Cc: reiserfs-list@namesys.com
Subject: Re: filesystem corruption ?
Date: Thu, 20 Mar 2003 20:06:39 +0300 [thread overview]
Message-ID: <20030320200639.A8618@namesys.com> (raw)
In-Reply-To: <200303201725.14039.bernd-schubert@web.de>
Hello!
On Thu, Mar 20, 2003 at 05:25:13PM +0100, Bernd Schubert wrote:
> We use this filesystem a nfs-root-fs to several clients (exported as
> read-only), so we are lucky, since we regularly backup the whole partition.
> We have a backup from this Morning and another one from Monday. Based on
> comparing the output of md5sum we can't find any problems between the version
> from monday and the version of this morning, *but* there are differences for
> some binaries in /usr/bin, such as gdb, between the backup of this Morning
> and the Current files.
Hm, interesting.
And what are the differences? How big are they?
Anything interesting in logs?
Any events happening between morning backup and time of problem discovery?
> Do you have any ideas whats going wrong and what we can do?
We need more info.
Also check modification date of gdb, may be some process changed it?
Bye,
Oleg
next prev parent reply other threads:[~2003-03-20 17:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 16:25 filesystem corruption ? Bernd Schubert
2003-03-20 17:06 ` Oleg Drokin [this message]
2003-03-20 18:23 ` Bernd Schubert
2003-03-21 7:32 ` Oleg Drokin
2003-03-21 10:14 ` Bernd Schubert
2003-03-21 13:01 ` Bernd Schubert
2003-03-21 13:07 ` Oleg Drokin
2003-03-21 13:20 ` Bernd Schubert
2003-03-21 16:00 ` Russell Coker
2003-03-21 17:14 ` Valdis.Kletnieks
2003-03-22 18:18 ` Bernd Schubert
2003-03-22 18:37 ` Anders Widman
-- strict thread matches above, loose matches on Subject: below --
2018-10-22 20:02 Filesystem corruption? Gervais, Francois
2018-10-22 23:12 ` Qu Wenruo
2018-10-23 9:25 ` Juergen Sauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030320200639.A8618@namesys.com \
--to=green@namesys.com \
--cc=bernd-schubert@web.de \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.