From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 16981] New: 2.6.36-rc1
Date: Tue, 24 Aug 2010 20:02:32 GMT [thread overview]
Message-ID: <bug-16981-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16981
Summary: 2.6.36-rc1
Product: IO/Storage
Version: 2.5
Kernel Version: 2.6.36-rc1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: SCSI
AssignedTo: linux-scsi@vger.kernel.org
ReportedBy: tv@fuzzy.cz
Regression: No
Created an attachment (id=27851)
--> (https://bugzilla.kernel.org/attachment.cgi?id=27851)
error when runing tune2fs on a LVM2/MD partition
After executing a tune2fs on a partition (LVM2 on top of an md-based raid1
device, with an ext3 filesystem on top of it), the kernel crashes - the
messages are available in the tune2fs.log attachment, the most interesting one
references a drivers/scsi/scsi_lib.c:1113.
When executing the same tune2fs command on a simple partition everything seems
to work fine, as well as when running it under an older kernel
(2.6.32-gentoo-r7).
I received a very similar error (on the same device, referencing the same piece
of code in scsi_lib.c) when running a filesystem check during boot (due to
reaching a predefined number of mounts). See the attachment 'boot.log'. Again,
this works under the older kernel.
I haven't tried the 2.6.36-r2 version (yet).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-08-24 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 20:02 bugzilla-daemon [this message]
2010-08-24 20:04 ` [Bug 16981] 2.6.36-rc1 bugzilla-daemon
2010-08-24 20:04 ` bugzilla-daemon
2010-08-24 20:11 ` bugzilla-daemon
2010-08-25 11:08 ` bugzilla-daemon
2012-05-12 16:11 ` bugzilla-daemon
2012-05-12 16:11 ` bugzilla-daemon
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=bug-16981-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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 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.