stripe_width should be sector_t to support large devices.
Signed-Off-By: Alasdair G Kergon [EMAIL PROTECTED]
--- diff/drivers/md/dm-stripe.c 2005-01-28 15:27:58.0 +
+++ source/drivers/md/dm-stripe.c 2005-01-28 15:28:23.0 +
@@ -21,7 +21,7 @@
uint32_t stripes
for dm-crypt and dm-raid1.
Signed-Off-By: Alasdair G Kergon [EMAIL PROTECTED]
--- diff/drivers/md/dm-crypt.c 2005-01-12 15:21:22.0 +
+++ source/drivers/md/dm-crypt.c2005-01-28 15:30:22.0 +
@@ -329,7 +329,7 @@
struct bio *base_bio, unsigned int
On Fri, Jan 21, 2005 at 03:57:38PM -0600, Kevin Corry wrote:
> On Friday 21 January 2005 3:20 pm, Roland Dreier wrote:
> > If I understand you correctly, do_div() (defined in )
I went for the simplest and safest fix first as this is a data
corruption problem and I want assurance that this fixes
On Fri, Jan 21, 2005 at 03:57:38PM -0600, Kevin Corry wrote:
On Friday 21 January 2005 3:20 pm, Roland Dreier wrote:
If I understand you correctly, do_div() (defined in asm/div64.h)
I went for the simplest and safest fix first as this is a data
corruption problem and I want assurance that this
Improve performance by optionally bypassing some code that uses bdget.
Signed-Off-By: Alasdair G Kergon <[EMAIL PROTECTED]>
--- diff/drivers/md/dm-ioctl.c 2005-01-12 20:50:16.0 +
+++ source/drivers/md/dm-ioctl.c2005-01-12 20:50:07.0 +
@@ -1,
Missing cast thought to cause data corruption on devices with stripes > ~1TB.
Signed-Off-By: Alasdair G Kergon <[EMAIL PROTECTED]>
--- diff/drivers/md/dm-stripe.c 2005-01-20 17:32:37.0 +
+++ source/drivers/md/dm-stripe.c 2005-01-20 17:32:26.0 +
@@ -179
G Kergon <[EMAIL PROTECTED]>
--- diff/drivers/md/dm-raid1.c 2005-01-12 15:21:22.0 +
+++ source/drivers/md/dm-raid1.c2005-01-12 18:57:08.0 +
@@ -1158,10 +1158,11 @@
return 0;
}
-static void mirror_suspend(struct dm_target *ti)
+stati
Remove unused bs_bio_init().
Signed-Off-By: Alasdair G Kergon <[EMAIL PROTECTED]>
--- diff/drivers/md/dm-io.c 2005-01-12 15:21:22.0 +
+++ source/drivers/md/dm-io.c 2005-01-12 18:58:09.0 +
@@ -149,22 +149,6 @@
return 0;
}
-static inline void bs_bi
Fix module reference counting for mirror log type.
Signed-Off-By: Alasdair G Kergon <[EMAIL PROTECTED]>
--- diff/drivers/md/dm-log.c2005-01-12 15:21:22.0 +
+++ source/drivers/md/dm-log.c 2005-01-12 18:55:17.0 +
@@ -17,9 +17,6 @@
int dm_register_dirty_lo
Fix module reference counting for mirror log type.
Signed-Off-By: Alasdair G Kergon [EMAIL PROTECTED]
--- diff/drivers/md/dm-log.c2005-01-12 15:21:22.0 +
+++ source/drivers/md/dm-log.c 2005-01-12 18:55:17.0 +
@@ -17,9 +17,6 @@
int dm_register_dirty_log_type(struct
Remove unused bs_bio_init().
Signed-Off-By: Alasdair G Kergon [EMAIL PROTECTED]
--- diff/drivers/md/dm-io.c 2005-01-12 15:21:22.0 +
+++ source/drivers/md/dm-io.c 2005-01-12 18:58:09.0 +
@@ -149,22 +149,6 @@
return 0;
}
-static inline void bs_bio_init
G Kergon [EMAIL PROTECTED]
--- diff/drivers/md/dm-raid1.c 2005-01-12 15:21:22.0 +
+++ source/drivers/md/dm-raid1.c2005-01-12 18:57:08.0 +
@@ -1158,10 +1158,11 @@
return 0;
}
-static void mirror_suspend(struct dm_target *ti)
+static void mirror_postsuspend
Improve performance by optionally bypassing some code that uses bdget.
Signed-Off-By: Alasdair G Kergon [EMAIL PROTECTED]
--- diff/drivers/md/dm-ioctl.c 2005-01-12 20:50:16.0 +
+++ source/drivers/md/dm-ioctl.c2005-01-12 20:50:07.0 +
@@ -1,6 +1,6
Missing cast thought to cause data corruption on devices with stripes ~1TB.
Signed-Off-By: Alasdair G Kergon [EMAIL PROTECTED]
--- diff/drivers/md/dm-stripe.c 2005-01-20 17:32:37.0 +
+++ source/drivers/md/dm-stripe.c 2005-01-20 17:32:26.0 +
@@ -179,7 +179,7
On Thu, Jan 20, 2005 at 03:22:14PM -0700, Trever L. Adams wrote:
> PV = the device
> VG = groups of them (the RAID5 array?)
> LV = what? the file system?
http://www.tldp.org/HOWTO/LVM-HOWTO/anatomy.html
http://www.novell.com/products/linuxenterpriseserver8/whitepapers/LVM.pdf
[Out-of-date now,
On Thu, Jan 20, 2005 at 10:40:02PM +0100, Norbert van Nobelen wrote:
> A logical volume in LVM will not handle more than 2TB. You can tie together
> the LVs in a volume group, thus going over the 2TB limit.
Confused over terminology?
Tie PVs together to form a VG, then divide VG up into LVs.
On Thu, Jan 20, 2005 at 10:40:02PM +0100, Norbert van Nobelen wrote:
A logical volume in LVM will not handle more than 2TB. You can tie together
the LVs in a volume group, thus going over the 2TB limit.
Confused over terminology?
Tie PVs together to form a VG, then divide VG up into LVs.
On Thu, Jan 20, 2005 at 03:22:14PM -0700, Trever L. Adams wrote:
PV = the device
VG = groups of them (the RAID5 array?)
LV = what? the file system?
http://www.tldp.org/HOWTO/LVM-HOWTO/anatomy.html
http://www.novell.com/products/linuxenterpriseserver8/whitepapers/LVM.pdf
[Out-of-date now,
501 - 518 of 518 matches
Mail list logo