Quoting Neil Brown <[EMAIL PROTECTED]>:
> 3/ Once you are satisfied that things look right, use
>mdadm --assemble /dev/md0 --update=byteorder
> to assemble the array.
This worked. After a lot of tries. I kept getting 'resource busy'
(or 'device busy' or something other in that
Quoting Neil Brown [EMAIL PROTECTED]:
3/ Once you are satisfied that things look right, use
mdadm --assemble /dev/md0 --update=byteorder
to assemble the array.
This worked. After a lot of tries. I kept getting 'resource busy'
(or 'device busy' or something other in that
Quoting Neil Brown <[EMAIL PROTECTED]>:
> This suggests that the superblock is currently the correct byteorder
> for the current host. You use
>mdadm --examine --metadata=0.swap /dev/sda1
> when you have moved a devices from one host to different host with the
> opposite endian-ness (e.g.
Quoting Neil Brown [EMAIL PROTECTED]:
This suggests that the superblock is currently the correct byteorder
for the current host. You use
mdadm --examine --metadata=0.swap /dev/sda1
when you have moved a devices from one host to different host with the
opposite endian-ness (e.g. bigendian
On Sunday July 8, [EMAIL PROTECTED] wrote:
> Quoting Neil Brown <[EMAIL PROTECTED]>:
>
> > Version 0.90 MD superblocks (still the default) uses host-endian
> > values so you cannot move between architectures directly. However
> > isn't too hard to make it work.
> > Firstly, use
> >mdadm
Quoting Neil Brown <[EMAIL PROTECTED]>:
> Version 0.90 MD superblocks (still the default) uses host-endian
> values so you cannot move between architectures directly. However
> isn't too hard to make it work.
> Firstly, use
>mdadm --examine --metadata=0.swap /dev/DEVICE
- s n i p -
Quoting Neil Brown [EMAIL PROTECTED]:
Version 0.90 MD superblocks (still the default) uses host-endian
values so you cannot move between architectures directly. However
isn't too hard to make it work.
Firstly, use
mdadm --examine --metadata=0.swap /dev/DEVICE
- s n i p -
ppc:~#
On Sunday July 8, [EMAIL PROTECTED] wrote:
Quoting Neil Brown [EMAIL PROTECTED]:
Version 0.90 MD superblocks (still the default) uses host-endian
values so you cannot move between architectures directly. However
isn't too hard to make it work.
Firstly, use
mdadm --examine
Quoting Neil Brown <[EMAIL PROTECTED]>:
> Firstly, use
>mdadm --examine --metadata=0.swap /dev/DEVICE
This should be done on the PPC, or can it be done on the Intel?
Tried this command on some other machines, and there the '--metadata'
is an unknown option... This on mdadm v1.9.0.
> Then
>
Quoting Neil Brown [EMAIL PROTECTED]:
Firstly, use
mdadm --examine --metadata=0.swap /dev/DEVICE
This should be done on the PPC, or can it be done on the Intel?
Tried this command on some other machines, and there the '--metadata'
is an unknown option... This on mdadm v1.9.0.
Then
> "Neil" == Neil Brown <[EMAIL PROTECTED]> writes:
Neil> On Saturday June 30, [EMAIL PROTECTED] wrote:
>> Quoting Alasdair G Kergon <[EMAIL PROTECTED]>:
>>
>> > On Thu, Jun 28, 2007 at 11:02:39PM +0200, Turbo Fredriksson wrote:
>> >> 2. How do I move a VG/PV/LV from PPC to x86?
>> >
>> >
Neil == Neil Brown [EMAIL PROTECTED] writes:
Neil On Saturday June 30, [EMAIL PROTECTED] wrote:
Quoting Alasdair G Kergon [EMAIL PROTECTED]:
On Thu, Jun 28, 2007 at 11:02:39PM +0200, Turbo Fredriksson wrote:
2. How do I move a VG/PV/LV from PPC to x86?
The on-disk LVM2 metadata
On Saturday June 30, [EMAIL PROTECTED] wrote:
> Quoting Alasdair G Kergon <[EMAIL PROTECTED]>:
>
> > On Thu, Jun 28, 2007 at 11:02:39PM +0200, Turbo Fredriksson wrote:
> >> 2. How do I move a VG/PV/LV from PPC to x86?
> >
> > The on-disk LVM2 metadata should be accessible from both
> >
Quoting Alasdair G Kergon <[EMAIL PROTECTED]>:
> On Thu, Jun 28, 2007 at 11:02:39PM +0200, Turbo Fredriksson wrote:
>> 2. How do I move a VG/PV/LV from PPC to x86?
>
> The on-disk LVM2 metadata should be accessible from both
> architectures.
Well, when I move the disks, the intel machine say
Quoting Alasdair G Kergon [EMAIL PROTECTED]:
On Thu, Jun 28, 2007 at 11:02:39PM +0200, Turbo Fredriksson wrote:
2. How do I move a VG/PV/LV from PPC to x86?
The on-disk LVM2 metadata should be accessible from both
architectures.
Well, when I move the disks, the intel machine say that one
On Saturday June 30, [EMAIL PROTECTED] wrote:
Quoting Alasdair G Kergon [EMAIL PROTECTED]:
On Thu, Jun 28, 2007 at 11:02:39PM +0200, Turbo Fredriksson wrote:
2. How do I move a VG/PV/LV from PPC to x86?
The on-disk LVM2 metadata should be accessible from both
architectures.
Well,
On Thu, Jun 28, 2007 at 11:02:39PM +0200, Turbo Fredriksson wrote:
> 2. How do I move a VG/PV/LV from PPC to x86?
The on-disk LVM2 metadata should be accessible from both
architectures.
Alasdair
--
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Thu, Jun 28, 2007 at 11:02:39PM +0200, Turbo Fredriksson wrote:
2. How do I move a VG/PV/LV from PPC to x86?
The on-disk LVM2 metadata should be accessible from both
architectures.
Alasdair
--
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to move some disks from my PPC desktop to a dedicated
server. Yesterday my system looked like this:
1. /dev/md0 372.61Gb (sda1+missing)
2. /dev/hdb 74.53Gb
3. /dev/sdb 298.09Gb
Now with the paycheck, I bought a third
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to move some disks from my PPC desktop to a dedicated
server. Yesterday my system looked like this:
1. /dev/md0 372.61Gb (sda1+missing)
2. /dev/hdb 74.53Gb
3. /dev/sdb 298.09Gb
Now with the paycheck, I bought a third
20 matches
Mail list logo
