2011-January Archive by Thread
Messages are ordered newest-to-oldest in this index. The newest
threads will be at the top of this page, the oldest will be at the bottom.
Within a single thread, the first mail note is the START of the
thread; the notes following that are in the chronological order of
when they were received. So globally, newest messages are at the top,
but within a thread, the oldest (the start of the thread) is at the
top.
If you think about it, it is confusing. Just go with the flow and everything will be all right.
- [dm-devel] [PATCH 1/2] dm mpath: fail message ioctl if specified path is not valid,
Mike Snitzer
- [dm-devel] Possible severe bug in the device mapper?,
Andreas Heinlein
- [dm-devel] [PATCH]: scsi_dh_rdac: fix BUG_ON in get_rdac_data from within send_mode_select,
Menny_Hamburger
- [dm-devel] nishant mungse wants to chat,
nishant mungse
- [dm-devel] How to find last sector of bio.,
nishant mungse
- [dm-devel] Doubt regarding dm-raid1,
nishant mungse
- [dm-devel] How to test the read/write flow of dm-target.,
nishant mungse
- [dm-devel] device-mapper, nishant mungse has invited you to open a Gmail account,
nishant mungse
- [dm-devel] Announcement: new device-mapper thin provisioning target with infrastructure online for review,
Heinz Mauelshagen
- [dm-devel] Improving dm-mirror as a final year project,
Miklos Vajna
- [dm-devel] [PATCH] multipath: reference count on pgpath,
Menny_Hamburger
- [dm-devel] multipath - reference count on pgpath,
Menny_Hamburger
- [dm-devel] multipath-tools ./multipath.conf.defaults libm ...,
bmarzins
- [dm-devel] [PATCH] [RFC] multipath: change the DEFAULT_MINIO for the request based multipath,
Malahal Naineni
- Re: [dm-devel] [PATCH] [RFC] multipath: change the DEFAULT_MINIO for the request based multipath,
Hannes Reinecke
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Mike Snitzer
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Jun'ichi Nomura
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Christophe Varoqui
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Mike Snitzer
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Christophe Varoqui
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Malahal Naineni
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Jun'ichi Nomura
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Malahal Naineni
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
nishant mungse
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
nishant mungse
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Christophe Varoqui
- Re: [dm-devel] multipath: change the DEFAULT_MINIO for the request based multipath,
Mike Snitzer
- Re: [dm-devel] [PATCH 14/49] drivers/md: Use vzalloc,
Mike Snitzer
- [dm-devel] help:"event number",
tom z
- Re: [dm-devel] [RFC PATCH 0/3] differentiate between I/O errors,
Mike Snitzer
- Re: [dm-devel] training mpath to discern between SCSI errors,
Mike Snitzer
- [dm-devel] [PATCH] Documentation: dm-crypt: update cryptsetup homepage,
Andrea Gelmini
- [dm-devel] [git pull] device-mapper patches for 2.6.38,
Alasdair G Kergon
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Milan Broz
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Jun'ichi Nomura
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Tejun Heo
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Milan Broz
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Karel Zak
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Tejun Heo
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Karel Zak
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Tejun Heo
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Milan Broz
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Tejun Heo
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Milan Broz
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Tejun Heo
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Theodore Tso
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
NeilBrown
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Ted Ts'o
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Tejun Heo
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Ted Ts'o
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Tejun Heo
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Milan Broz
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Tejun Heo
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Kay Sievers
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Milan Broz
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Jun'ichi Nomura
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Karel Zak
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Kay Sievers
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Karel Zak
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Kay Sievers
- Re: [dm-devel] linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
Tejun Heo
- [dm-devel] [PATCH] block: restore multiple bd_link_disk_holder() support,
Tejun Heo
- [dm-devel] What is the status of RAID5 support with pdc (AMD SB850 Southbridge) hardware?,
Mantas Kriaučiūnas
- [dm-devel] Fw: linux-next - WARNING: at fs/block_dev.c:824 bd_link_disk_holder+0x92/0x1ac(),
NeilBrown
- Re: [dm-devel] linux-next: Tree for January 12 (dm-crypt),
Randy Dunlap
- Re: [dm-devel] [PATCH]md:dm.c Fix warning: statement with no effect,
Mike Snitzer
- [dm-devel] [PATCH v4] dm mpath: delay retry of activate_path on SCSI_DH_RETRY,
Mike Snitzer
- [dm-devel] PROBLEM: SSD access time with dm-crypt is way too high,
Michael Zugelder
- [dm-devel] trim support (discard),
Jens Kasten
- [dm-devel] kobject_put vs module unload,
Mikulas Patocka
- Re: [dm-devel] [PATCH 6/6] dm-snap-persistent: make metadata_wq multithreaded,
Mikulas Patocka
- [dm-devel] Patch to issue pure flushes directly (Was: Re: [PATCH v6 0/4] ext4: Coordinate data-only flush requests sent) by fsync,
Ted Ts'o
- Re: [dm-devel] [PATCH 1/6] dm-stripe: drop kstriped,
Alasdair G Kergon
- [dm-devel] [PATCH v2] dm log: use PTR_ERR value instead of -ENOMEM,
Mike Snitzer
- Re: [dm-devel] [patch] md/dm-log: use PTR_ERR value instead of -ENOMEM,
Jonathan Brassow
- [dm-devel] [PATCH v2] dm: remove superfluous irq disablement in dm_request_fn,
Mike Snitzer
- [dm-devel] [PATCH v3] dm mpath: delay retry of activate_path on SCSI_DH_RETRY,
Mike Snitzer
- [dm-devel] [PATCH v2] dm snapshot: avoid storing private suspended state,
Mike Snitzer
- [dm-devel] [PATCH 0/3 v2] dm crypt: add Loop-AES compatibility mode support,
Milan Broz
- [dm-devel] [PATCH] dm: move device check warning messages into debug level,
Milan Broz
- Re: [dm-devel] hunt for 2.6.37 dm-crypt+ext4 corruption?,
Heinz Diehl
- Re: [dm-devel] [PATCH v3 0/8] dm-raid (raid456) target,
Mike Snitzer
- [dm-devel] [PATCH] Make kcopyd merge more I/O requests,
Mikulas Patocka
- Re: [dm-devel] [PATCH wq#for-2.6.38] workqueue: use WQ_MEM_RECLAIM instead of WQ_RESCUER,
Steven Whitehouse