On 01/23/2009 11:28 AM, Mike Castle wrote:
On Wed, Jan 21, 2009 at 8:13 PM, Ron Johnson wrote:
If I have lots of existing data in JBODs, would I create a PV and VG on the
new drive, mv all the data from the existing drives to the new VG, then add
my existing drives (while also enlarging the fs)
On Wed, Jan 21, 2009 at 8:13 PM, Ron Johnson wrote:
>
> If I have lots of existing data in JBODs, would I create a PV and VG on the
> new drive, mv all the data from the existing drives to the new VG, then add
> my existing drives (while also enlarging the fs) to the one-drive VG, thus
> making an
On 01/21/2009 11:30 PM, Matthew Moore wrote:
On Wednesday 21 January 2009 09:13:07 pm Ron Johnson wrote:
If I have lots of existing data in JBODs, would I create a PV and VG
on the new drive, mv all the data from the existing drives to the
new VG, then add my existing drives (while also enlargin
On 01/22/2009 11:20 AM, Douglas A. Tutty wrote:
On Thu, Jan 22, 2009 at 12:24:45AM -0600, Ron Johnson wrote:
On 01/21/2009 11:30 PM, Matthew Moore wrote:
On Wednesday 21 January 2009 09:13:07 pm Ron Johnson wrote:
That is exactly what I would do. Everyone warns about how cataclysmic
things w
On Thu, Jan 22, 2009 at 12:24:45AM -0600, Ron Johnson wrote:
> On 01/21/2009 11:30 PM, Matthew Moore wrote:
> >On Wednesday 21 January 2009 09:13:07 pm Ron Johnson wrote:
> >That is exactly what I would do. Everyone warns about how cataclysmic
> >things will happen because your new uber-device ha
On 01/21/2009 11:30 PM, Matthew Moore wrote:
On Wednesday 21 January 2009 09:13:07 pm Ron Johnson wrote:
If I have lots of existing data in JBODs, would I create a PV and VG
on the new drive, mv all the data from the existing drives to the
new VG, then add my existing drives (while also enlargin
On Wednesday 21 January 2009 09:13:07 pm Ron Johnson wrote:
> If I have lots of existing data in JBODs, would I create a PV and VG
> on the new drive, mv all the data from the existing drives to the
> new VG, then add my existing drives (while also enlarging the fs) to
> the one-drive VG, thus maki
On 01/21/2009 09:59 PM, Matthew Moore wrote:
On Wednesday 21 January 2009 08:43:02 pm Ron Johnson wrote:
1. Since sdX device names are non-deterministic, can I use it with
devices specified as UUIDs? Or does lvm handle that for me on boot?
lvm stores volume identifiers in a header at the star
On Wednesday 21 January 2009 08:43:02 pm Ron Johnson wrote:
> 1. Since sdX device names are non-deterministic, can I use it with
> devices specified as UUIDs? Or does lvm handle that for me on boot?
lvm stores volume identifiers in a header at the start of the physical
volumes, so the device nam
Hi,
I'm about to get a 1TB drive which I will use as the basis of an lvm
set.
1. Since sdX device names are non-deterministic, can I use it with
devices specified as UUIDs? Or does lvm handle that for me on boot?
2. Why should I partitioning this drive into smaller chunks if
they're all going
10 matches
Mail list logo
