From: joe briggs <jbriggs@briggsmedia.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: massive file system corruption after loading dhcp,bind,qpopper, and sendmail
Date: Sat, 14 Jun 2003 17:15:23 -0400 [thread overview]
Message-ID: <200306141715.23702.jbriggs@briggsmedia.com> (raw)
I have several machines deployed with identical Debian Woody distros and
2.4.19 kernel. I send these boxes out after following a written load & build
procedure and master cdrom built from a gold standard. They all have a
single 40 GB ide for the system/os drive, and a Promise or 3ware 2x ide raid
controller with 2 striped ide drives. I use ReiserFS all around. When a
location needs business continuity services (sendmail, dhcp, bind, and
qpopper), I apt-get'em and then follow up with a "apt-get update" and
"apt-get upgrade". This has worked well over the last year. However, this
last 30 days, I had a couple of machines that I upgraded with this procedure,
and within hours I started getting massive reiserfs errors on the system
drive and if rebooted, won't come all the way up - getting stuck trying to
load some module. If I boot off of my recovery CDROM and "reiserfsck
--fix-fixable /dev/hda2" (hda2 is where I am mounted) I get tons of errors.
On a hunch I followed the procedure to build a fresh system, but downloaded
2.4.21 and built it with the same .config file as my 2.4.19, and installed
this before getting the downloads (dhcp, bind, ...). Problem dissappeared!
Is is possible that one or more of those .deb files where built within the
last 30 days or so, and has some very bad problem?
--
Joe Briggs
Briggs Media Systems
105 Burnsen Ave.
Manchester NH 01304 USA
TEL/FAX 603-232-3115 MOBILE 603-493-2386
www.briggsmedia.com
reply other threads:[~2003-06-14 20:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200306141715.23702.jbriggs@briggsmedia.com \
--to=jbriggs@briggsmedia.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®