From: Dale Amon <amon@vnl.com>
To: Dale Amon <amon@vnl.com>, linux-kernel@vger.kernel.org
Subject: Re: Problem with ufs nextstep in 2.6.18 (debian)
Date: Mon, 16 Apr 2007 00:11:51 +0100 [thread overview]
Message-ID: <20070415231151.GC5129@vnl.com> (raw)
In-Reply-To: <20070415013848.GG4770@vnl.com>
The error also happens in 2.6.19, same as in 2.6.18. I
extracted this from syslog:
Apr 17 00:14:08 kdev kernel: loop: loaded (max 8 devices)
Apr 17 00:14:15 kdev kernel: UFS-fs error (device loop0): ufs_check_page: bad entry in directory #2: directory entry across blocks - offset=356, rec_len=668, name_len=19
Apr 17 00:14:15 kdev kernel: UFS-fs error (device loop0): ufs_readdir: bad page in #2
next prev parent reply other threads:[~2007-04-15 23:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 1:38 Problem with ufs nextstep in 2.6.18 (debian) Dale Amon
2007-04-15 23:11 ` Dale Amon [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-16 7:32 Evgeniy Dushistov
2007-04-16 16:04 ` Dale Amon
2007-04-17 1:10 ` Dale Amon
2007-04-19 16:39 ` Dale Amon
2007-11-20 20:29 Dave Bailey
2007-11-21 15:37 ` Jan Kara
2007-11-22 4:19 ` Evgeniy Dushistov
2007-11-25 1:26 Dave Bailey
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=20070415231151.GC5129@vnl.com \
--to=amon@vnl.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