From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: viro@math.psu.edu
Cc: linux-kernel@vger.kernel.org
Subject: [false alarm] Re: 2.5.0 breakage even with fix?
Date: Sat, 24 Nov 2001 01:13:55 MET-1 [thread overview]
Message-ID: <A0AC5B46636@vcnet.vc.cvut.cz> (raw)
On 24 Nov 01 at 1:05, Petr Vandrovec wrote:
> do not have coherent /dev/hda3 cache, I have no idea how to read
> real contents of /var/lib/dpkg/tmp.ci, but
> ls -l /var/lib/dpkg/tmp.ci/ reemited error message about
> ext2-fs error, so I think that it is real problem, and my tmp.ci directory
> contains some file contents instead. And I'm 100% sure that
> /var/lib/dpkg/tmp.ci was created with patched kernel :-(
I deeply apologize. I added one '!' into patch by mistake, so
my 'patched' kernel released inodes on MS_ACTIVE systems back
as free :-(
Sorry for confusion,
Petr Vandrovec
vandrove@vc.cvut.cz
reply other threads:[~2001-11-24 0:14 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=A0AC5B46636@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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