From: Christoph Hellwig <hch@lst.de>
To: joern@logfs.org
Cc: linux-fsdevel@vger.kernel.org
Subject: fun with logfs
Date: Sat, 14 Aug 2010 16:44:43 +0200 [thread overview]
Message-ID: <20100814144443.GA22920@lst.de> (raw)
Trying to mount a partition which I've recently wiped using pvremove:
qemu1:~# mount -o delaylog,logbsize=262144 /dev/vdb6 /mnt/
[ 177.032171] FAT: Unrecognized mount option "delaylog" or missing value
[ 177.037618] VFS: could not find a valid V7 on vdb6.
[ 177.041762] BUG: unable to handle kernel NULL pointer dereference at 00000004
[ 177.043942] IP: [<c072e1d7>] __list_add+0x7/0xa0
[ 177.045620] *pde = 00000000
[ 177.045648] Oops: 0000 [#1] SMP
[ 177.045648] last sysfs file: /sys/devices/virtio-pci/virtio1/block/vdb/removable
Entering kdb (current=0xf79d7070, pid 2858) on processor 0 Oops: (null) due to oops @ 0xc072e1d7
<d>Modules linked in:
<c>
<d>Pid: 2858, comm: mount Not tainted 2.6.35+ #307 /Bochs
<d>EIP: 0060:[<c072e1d7>] EFLAGS: 00010282 CPU: 0 EIP is at __list_add+0x7/0xa0
<d>EAX: f18c9eb8 EBX: f18c9bf8 ECX: 00000000 EDX: f5e8d2cc
<d>ESI: f5e8d000 EDI: ffffffea EBP: f5fa5e5c ESP: f5fa5e34
<d> DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
<0>Process mount (pid: 2858, ti=f5fa4000 task=f79d7070 task.ti=f5fa4000)
<0>Stack: c0d66990 ffffffea f5fa5e5c c09caa7c 00000000 00000002 00000000 c044717d
<0> f18c9bf8 f18c9bf8 f5fa5e6c c04471a5 f18c9bf8 f5fbc970 f5fa5e7c c0222350
<0> f5e8d000 f5fbc970 f5fa5eb4 c044f6f8 00000000 00000000 c0237d33 f544a6f8
<0>Call Trace:
<0> [<c09caa7c>] ? _raw_spin_lock+0x5c/0x70
<0> [<c044717d>] ? logfs_drop_inode+0x1d/0x60
<0> [<c04471a5>] ? logfs_drop_inode+0x45/0x60
<0> [<c0222350>] ? iput+0x50/0x260
<0> [<c044f6f8>] ? logfs_get_sb_device+0x168/0x670
<0> [<c0237d33>] ? bd_finish_claiming+0x63/0x80
[0]more>
reply other threads:[~2010-08-14 14:44 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=20100814144443.GA22920@lst.de \
--to=hch@lst.de \
--cc=joern@logfs.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).