Re: Network interface "stops working"

[Turbo Fredriksson]

Not sure it’s a bug yet, but anyone have any ideas on how I can find out?

> On 22 Jan 2018, at 23:32, Cong Wang <xiyou.wangc...@gmail.com> wrote:
> 
> (Please always Cc netdev for networking related bugs.)
> 
> On Mon, Jan 22, 2018 at 2:02 AM, Turbo Fredriksson <tu...@bayour.com> wrote:
>> I just got a new broadband delivered at home. It is "Hyperoptic 1Gbps fiber" 
>> which comes as a ethernet connector at home. I wasn’t around
>> when they connected up everything, so I’m not sure *where* the fiber starts, 
>> but either way, I have an ethernet jack in one of my rooms.
>> 
>> They also provided me with a ZTE router. I have need for my own services 
>> (firewalling, NATing, IPSEC and what not), so don’t want to use
>> the provided router..
>> 
>> However, I’m having serious trouble keeping the interface up! Works for a 
>> few minutes and then just “stops working”. Don’t know why, there’s
>> nothing in the logs or from dmesg..
>> 
>> Taking the interface down and then up again usually solves it. For a few 
>> minutes.
>> 
>> Also, when running the interface (a Intel 82576 Gigabit dual port, using the 
>> igb driver - tried e1000 and e1000e but they don’t find any interfaces),
>> in 1Gbps mode, the interface starts flapping up and down and I can’t get a 
>> connection at all. So my interface definition runs a script to use
>> ethtool to set the speed to 100Mbps, full duplex, no auto negotiation. Which 
>> “kinda” works (for a while, hence my problems).
>> 
>> Because the provided router works just fine, I’m sure it’s something on my 
>> Linux box (Debian GNU/Linux Jessie) that does it.. I’ve tried running
>> it without any iptables, in both static and DHCP mode but same problem..
>> 
>> I’m not a complete beginner with Linux nor networks, but this is to “close 
>> to the hardware” for me. I’m at a loss to what else to try..
>> 
>> This isn’t a new machine, it have served me very well for five years give or 
>> take and I’ve never had any problems with it (not to say that it still
>> can’t be hardware problems, but I find that somewhat unlikely at the moment).
>> 
>> 
>> Could anyone please advice to what I can try to try to pinpoint the problem 
>> (and/or possibly fix it)?



signature.asc
Description: Message signed with OpenPGP

Re: Network interface "stops working"

[Turbo Fredriksson]

Not sure it’s a bug yet, but anyone have any ideas on how I can find out?

> On 22 Jan 2018, at 23:32, Cong Wang  wrote:
> 
> (Please always Cc netdev for networking related bugs.)
> 
> On Mon, Jan 22, 2018 at 2:02 AM, Turbo Fredriksson  wrote:
>> I just got a new broadband delivered at home. It is "Hyperoptic 1Gbps fiber" 
>> which comes as a ethernet connector at home. I wasn’t around
>> when they connected up everything, so I’m not sure *where* the fiber starts, 
>> but either way, I have an ethernet jack in one of my rooms.
>> 
>> They also provided me with a ZTE router. I have need for my own services 
>> (firewalling, NATing, IPSEC and what not), so don’t want to use
>> the provided router..
>> 
>> However, I’m having serious trouble keeping the interface up! Works for a 
>> few minutes and then just “stops working”. Don’t know why, there’s
>> nothing in the logs or from dmesg..
>> 
>> Taking the interface down and then up again usually solves it. For a few 
>> minutes.
>> 
>> Also, when running the interface (a Intel 82576 Gigabit dual port, using the 
>> igb driver - tried e1000 and e1000e but they don’t find any interfaces),
>> in 1Gbps mode, the interface starts flapping up and down and I can’t get a 
>> connection at all. So my interface definition runs a script to use
>> ethtool to set the speed to 100Mbps, full duplex, no auto negotiation. Which 
>> “kinda” works (for a while, hence my problems).
>> 
>> Because the provided router works just fine, I’m sure it’s something on my 
>> Linux box (Debian GNU/Linux Jessie) that does it.. I’ve tried running
>> it without any iptables, in both static and DHCP mode but same problem..
>> 
>> I’m not a complete beginner with Linux nor networks, but this is to “close 
>> to the hardware” for me. I’m at a loss to what else to try..
>> 
>> This isn’t a new machine, it have served me very well for five years give or 
>> take and I’ve never had any problems with it (not to say that it still
>> can’t be hardware problems, but I find that somewhat unlikely at the moment).
>> 
>> 
>> Could anyone please advice to what I can try to try to pinpoint the problem 
>> (and/or possibly fix it)?



signature.asc
Description: Message signed with OpenPGP

Network interface "stops working"

[Turbo Fredriksson]

I just got a new broadband delivered at home. It is "Hyperoptic 1Gbps fiber" 
which comes as a ethernet connector at home. I wasn’t around
when they connected up everything, so I’m not sure *where* the fiber starts, 
but either way, I have an ethernet jack in one of my rooms.

They also provided me with a ZTE router. I have need for my own services 
(firewalling, NATing, IPSEC and what not), so don’t want to use
the provided router..

However, I’m having serious trouble keeping the interface up! Works for a few 
minutes and then just “stops working”. Don’t know why, there’s
nothing in the logs or from dmesg..

Taking the interface down and then up again usually solves it. For a few 
minutes.

Also, when running the interface (a Intel 82576 Gigabit dual port, using the 
igb driver - tried e1000 and e1000e but they don’t find any interfaces),
in 1Gbps mode, the interface starts flapping up and down and I can’t get a 
connection at all. So my interface definition runs a script to use
ethtool to set the speed to 100Mbps, full duplex, no auto negotiation. Which 
“kinda” works (for a while, hence my problems).

Because the provided router works just fine, I’m sure it’s something on my 
Linux box (Debian GNU/Linux Jessie) that does it.. I’ve tried running
it without any iptables, in both static and DHCP mode but same problem..

I’m not a complete beginner with Linux nor networks, but this is to “close to 
the hardware” for me. I’m at a loss to what else to try..

This isn’t a new machine, it have served me very well for five years give or 
take and I’ve never had any problems with it (not to say that it still
can’t be hardware problems, but I find that somewhat unlikely at the moment).


Could anyone please advice to what I can try to try to pinpoint the problem 
(and/or possibly fix it)?


signature.asc
Description: Message signed with OpenPGP

Network interface "stops working"

[Turbo Fredriksson]

I just got a new broadband delivered at home. It is "Hyperoptic 1Gbps fiber" 
which comes as a ethernet connector at home. I wasn’t around
when they connected up everything, so I’m not sure *where* the fiber starts, 
but either way, I have an ethernet jack in one of my rooms.

They also provided me with a ZTE router. I have need for my own services 
(firewalling, NATing, IPSEC and what not), so don’t want to use
the provided router..

However, I’m having serious trouble keeping the interface up! Works for a few 
minutes and then just “stops working”. Don’t know why, there’s
nothing in the logs or from dmesg..

Taking the interface down and then up again usually solves it. For a few 
minutes.

Also, when running the interface (a Intel 82576 Gigabit dual port, using the 
igb driver - tried e1000 and e1000e but they don’t find any interfaces),
in 1Gbps mode, the interface starts flapping up and down and I can’t get a 
connection at all. So my interface definition runs a script to use
ethtool to set the speed to 100Mbps, full duplex, no auto negotiation. Which 
“kinda” works (for a while, hence my problems).

Because the provided router works just fine, I’m sure it’s something on my 
Linux box (Debian GNU/Linux Jessie) that does it.. I’ve tried running
it without any iptables, in both static and DHCP mode but same problem..

I’m not a complete beginner with Linux nor networks, but this is to “close to 
the hardware” for me. I’m at a loss to what else to try..

This isn’t a new machine, it have served me very well for five years give or 
take and I’ve never had any problems with it (not to say that it still
can’t be hardware problems, but I find that somewhat unlikely at the moment).


Could anyone please advice to what I can try to try to pinpoint the problem 
(and/or possibly fix it)?


signature.asc
Description: Message signed with OpenPGP

unmap/blacklist memory page?

[Turbo Fredriksson]

I've been reading 


http://spectrum.ieee.org/computing/hardware/drams-damning-defects-and-how-they-cripple-computers

today, and although much of it I did know, the fact that it
seems that hard errors are much more common that previously
thought surprised me. And worried me…


I've managed to figure out (I think) how to monitor this
(mcelog), how to actually, live (!!), manage to unmap/blacklist
a sector/page is something I haven't managed to google…

The only thing I've managed to find is how to do this on the
boot prompt/grub config and that's "to late"…

Is there any command that will allow me to do this from the
command line?


I've been looking at the 'edac' module(s), but my

/sys/devices/system/edac/mc

directory is empty (and I don't have a .../pci dir either).

I have both the 'edac_core' and 'i7core_edac' loaded. Do I
need any else? Can't find any in /lib/modules/`uname -r` that
seems to fit the bill…

But in any case, that seems to be reporting only anyway… ?
-- 
Try not. Do. Or do not. There is no try!
- Yoda

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

unmap/blacklist memory page?

[Turbo Fredriksson]

I've been reading 


http://spectrum.ieee.org/computing/hardware/drams-damning-defects-and-how-they-cripple-computers

today, and although much of it I did know, the fact that it
seems that hard errors are much more common that previously
thought surprised me. And worried me…


I've managed to figure out (I think) how to monitor this
(mcelog), how to actually, live (!!), manage to unmap/blacklist
a sector/page is something I haven't managed to google…

The only thing I've managed to find is how to do this on the
boot prompt/grub config and that's "to late"…

Is there any command that will allow me to do this from the
command line?


I've been looking at the 'edac' module(s), but my

/sys/devices/system/edac/mc

directory is empty (and I don't have a .../pci dir either).

I have both the 'edac_core' and 'i7core_edac' loaded. Do I
need any else? Can't find any in /lib/modules/`uname -r` that
seems to fit the bill…

But in any case, that seems to be reporting only anyway… ?
-- 
Try not. Do. Or do not. There is no try!
- Yoda

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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 effect. But eventually
I got all my MD's moved.

Thanx for all the help.
-- 
Rule Psix Mossad class struggle tritium DES counter-intelligence
Treasury fissionable NORAD Kennedy smuggle genetic cracking subway
pits
[See http://www.aclu.org/echelonwatch/index.html for more about this]
[Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf]
If neither of these works, try http://www.aclu.org and search for echelon.
Note. This is a real, not fiction.
http://www.theregister.co.uk/2001/09/06/eu_releases_echelon_spying_report/
http://www.aclu.org/safefree/nsaspying/23989res20060131.html#echelon
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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 effect. But eventually
I got all my MD's moved.

Thanx for all the help.
-- 
Rule Psix Mossad class struggle tritium DES counter-intelligence
Treasury fissionable NORAD Kennedy smuggle genetic cracking subway
pits
[See http://www.aclu.org/echelonwatch/index.html for more about this]
[Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf]
If neither of these works, try http://www.aclu.org and search for echelon.
Note. This is a real, not fiction.
http://www.theregister.co.uk/2001/09/06/eu_releases_echelon_spying_report/
http://www.aclu.org/safefree/nsaspying/23989res20060131.html#echelon
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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 to littlendian).

I see, thanx for clarifying this.

> Does that make it clear?

Absolutely. I just want to be very clear. I don't have a full backup
(have no means to backup 1Tb), so I want to minimize the risk of loosing
data. I thank you for explaining so that even I can understand :)




PS. No sarcasm intended, even IF it should sound like it! I _am_ greatfull.
-- 
Noriega Honduras Marxist South Africa president AK-47 FSF radar FBI
congress class struggle SEAL Team 6 colonel Cocaine DES
[See http://www.aclu.org/echelonwatch/index.html for more about this]
[Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf]
If neither of these works, try http://www.aclu.org and search for echelon.
Note. This is a real, not fiction.
http://www.theregister.co.uk/2001/09/06/eu_releases_echelon_spying_report/
http://www.aclu.org/safefree/nsaspying/23989res20060131.html#echelon
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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 to littlendian).

I see, thanx for clarifying this.

 Does that make it clear?

Absolutely. I just want to be very clear. I don't have a full backup
(have no means to backup 1Tb), so I want to minimize the risk of loosing
data. I thank you for explaining so that even I can understand :)




PS. No sarcasm intended, even IF it should sound like it! I _am_ greatfull.
-- 
Noriega Honduras Marxist South Africa president AK-47 FSF radar FBI
congress class struggle SEAL Team 6 colonel Cocaine DES
[See http://www.aclu.org/echelonwatch/index.html for more about this]
[Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf]
If neither of these works, try http://www.aclu.org and search for echelon.
Note. This is a real, not fiction.
http://www.theregister.co.uk/2001/09/06/eu_releases_echelon_spying_report/
http://www.aclu.org/safefree/nsaspying/23989res20060131.html#echelon
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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:~# mdadm --examine --metadata=0.swap /dev/md0
mdadm: No super block found on /dev/md0 (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/md1
mdadm: No super block found on /dev/md1 (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/md2
mdadm: No super block found on /dev/md2 (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/sda1
mdadm: No super block found on /dev/sda1 (Expected magic a92b4efc, got fc4e2ba9)
ppc:~# mdadm --examine --metadata=0.swap /dev/sda
mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/sdb
mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/sdb1
mdadm: No super block found on /dev/sdb1 (Expected magic a92b4efc, got fc4e2ba9)
ppc:~# mdadm --examine --metadata=0.swap /dev/sdc
mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/sdc1
mdadm: No super block found on /dev/sdc1 (Expected magic a92b4efc, got fc4e2ba9)
ppc:~# cat /proc/mdstat | grep ^md
md2 : active raid1 sdb1[0]
md1 : active raid1 sdc1[0]
md0 : active raid1 sda1[0]
- s n i p -

Now what?

> to check that you have the right devices.
> Then
>
>   mdadm --assemble /dev/md0 --update=byteorder /dev/DEV0 /dev/DEV1  
>
> That should assemble the array and update the superblocks so that they
> are in the right byteorder and will assemble easily in future.

Is this safe, changing the byteorder on all the physical devices (that are
part of my MD's)?
Will it still work on the PPC?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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:~# mdadm --examine --metadata=0.swap /dev/md0
mdadm: No super block found on /dev/md0 (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/md1
mdadm: No super block found on /dev/md1 (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/md2
mdadm: No super block found on /dev/md2 (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/sda1
mdadm: No super block found on /dev/sda1 (Expected magic a92b4efc, got fc4e2ba9)
ppc:~# mdadm --examine --metadata=0.swap /dev/sda
mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/sdb
mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/sdb1
mdadm: No super block found on /dev/sdb1 (Expected magic a92b4efc, got fc4e2ba9)
ppc:~# mdadm --examine --metadata=0.swap /dev/sdc
mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got )
ppc:~# mdadm --examine --metadata=0.swap /dev/sdc1
mdadm: No super block found on /dev/sdc1 (Expected magic a92b4efc, got fc4e2ba9)
ppc:~# cat /proc/mdstat | grep ^md
md2 : active raid1 sdb1[0]
md1 : active raid1 sdc1[0]
md0 : active raid1 sda1[0]
- s n i p -

Now what?

 to check that you have the right devices.
 Then

   mdadm --assemble /dev/md0 --update=byteorder /dev/DEV0 /dev/DEV1  

 That should assemble the array and update the superblocks so that they
 are in the right byteorder and will assemble easily in future.

Is this safe, changing the byteorder on all the physical devices (that are
part of my MD's)?
Will it still work on the PPC?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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
>   mdadm --assemble /dev/md0 --update=byteorder /dev/DEV0 /dev/DEV1  

And this on the Intel?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Forcibly remove broken disk from LV

[Turbo Fredriksson]

Quoting "Jesper Juhl" <[EMAIL PROTECTED]>:

> On 04/07/07, Jesper Juhl <[EMAIL PROTECTED]> wrote:
>> On 04/07/07, Turbo Fredriksson <[EMAIL PROTECTED]> wrote:
>> > I have a disk that only gives SCSI errors etc which
>> > I want to remove from the VG. But vgreduce only hangs
>> > and so does pvremove...
>> >
>> > If I physically remove the disk, the vg/pv/lv etc isn't
>> > accessible so the vgreduce won't work (claims that it
>> > can't find any PV's etc).
>> >
>> > So how do I remove the disk?
>>
>> vgreduce --removemissing
>>
>> should do the trick I'd say.

Just hangs. I gues I must first cancel the pvmove...

> Ohh and by the way, pvremove also has a --force option - if needed.

Also just hangs...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Forcibly remove broken disk from LV

[Turbo Fredriksson]

Quoting Jesper Juhl [EMAIL PROTECTED]:

 On 04/07/07, Jesper Juhl [EMAIL PROTECTED] wrote:
 On 04/07/07, Turbo Fredriksson [EMAIL PROTECTED] wrote:
  I have a disk that only gives SCSI errors etc which
  I want to remove from the VG. But vgreduce only hangs
  and so does pvremove...
 
  If I physically remove the disk, the vg/pv/lv etc isn't
  accessible so the vgreduce won't work (claims that it
  can't find any PV's etc).
 
  So how do I remove the disk?

 vgreduce --removemissing

 should do the trick I'd say.

Just hangs. I gues I must first cancel the pvmove...

 Ohh and by the way, pvremove also has a --force option - if needed.

Also just hangs...
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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
   mdadm --assemble /dev/md0 --update=byteorder /dev/DEV0 /dev/DEV1  

And this on the Intel?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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 of
the disks don't have a partition table and that the other don't
have any MD superblock...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

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 of
the disks don't have a partition table and that the other don't
have any MD superblock...
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

-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 SATA disk (400Gb). I new from
the start that disk wouldn't fit in my desktopbox, so I also bought a
500W PSU (I had a huge server case without PSU from previously).

I was a little impatient, so I added the new disk (physically just
dangling outside the box :) to the LVM (as md1+missing).

The idea was to re-create sdb as mdX+missing, so I tried pvmove sdb.
But instantly received a lot of errors. Now I can't remove it
from the VG!

My new server is a i386, and I already had a disk with Linux installed
for Intel, so that disk was also moved (from another server I don't
need any more - it was a Pentium 1 - to slow! :).

In with the system disk, in with the LVM disk and started. The system
had to be upgraded (from Ubuntu 6.xx to 7.04 - Feisty). Took a couple
of hours, and when that was done, I started to get the MD's working.
No go... One of the disks didn't even have a partition table!? None
of the disks had a MD superblock!

I wasn't really scared, I knew I haven't tried to modify the disks.
Put everything back into the PPC, and yes, everything works as
expected (exept the read errors from sdc/md1).


So, long winded explanation of what i've done, any idea about:

  1. How do I remove md1/sdc before I get data on it (i have the
 LVM unmounted for the time being).

  2. How do I move a VG/PV/LV from PPC to x86?
 I.e., how do I fix/solve/get around the problem with endianness
 so I can move the disks between the machines?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 

iD8DBQFGhCHomlWzPKccHgARApC7AJ9eFBMpNObARyIiFptbwChKCWzaXACfSr6z
m6k0jAvBS0PtC/1Is8OWTvk=
=qrJb
-END PGP SIGNATURE-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Moving MD/LVM from PPC to x86

[Turbo Fredriksson]

-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 SATA disk (400Gb). I new from
the start that disk wouldn't fit in my desktopbox, so I also bought a
500W PSU (I had a huge server case without PSU from previously).

I was a little impatient, so I added the new disk (physically just
dangling outside the box :) to the LVM (as md1+missing).

The idea was to re-create sdb as mdX+missing, so I tried pvmove sdb.
But instantly received a lot of errors. Now I can't remove it
from the VG!

My new server is a i386, and I already had a disk with Linux installed
for Intel, so that disk was also moved (from another server I don't
need any more - it was a Pentium 1 - to slow! :).

In with the system disk, in with the LVM disk and started. The system
had to be upgraded (from Ubuntu 6.xx to 7.04 - Feisty). Took a couple
of hours, and when that was done, I started to get the MD's working.
No go... One of the disks didn't even have a partition table!? None
of the disks had a MD superblock!

I wasn't really scared, I knew I haven't tried to modify the disks.
Put everything back into the PPC, and yes, everything works as
expected (exept the read errors from sdc/md1).


So, long winded explanation of what i've done, any idea about:

  1. How do I remove md1/sdc before I get data on it (i have the
 LVM unmounted for the time being).

  2. How do I move a VG/PV/LV from PPC to x86?
 I.e., how do I fix/solve/get around the problem with endianness
 so I can move the disks between the machines?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 http://mailcrypt.sourceforge.net/

iD8DBQFGhCHomlWzPKccHgARApC7AJ9eFBMpNObARyIiFptbwChKCWzaXACfSr6z
m6k0jAvBS0PtC/1Is8OWTvk=
=qrJb
-END PGP SIGNATURE-
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Weird harddisk behaviour

[Turbo Fredriksson]

when there is no longer anything to take away.
   -- Antoine de Saint-Exupery
Date: Sat, 20 Jan 2007 20:58:17 +0100
In-Reply-To: <[EMAIL PROTECTED]> (Ken Moffat's message of
 "Thu, 18 Jan 2007 00:18:38 +")
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/20.7 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Quoting Ken Moffat <[EMAIL PROTECTED]>:

>  So, you were using a valid tool, but what you put in your original
> mail shows garbage - something like apple_partition_ma[mamama...

That's what fdisk showed me. I don't have a true UTF-8 system, so when
cutting-and-pasing between the shell and mail app, it might have been
distorted. But the output WAS weird!

> But if it isn't, somehow the data on the disk (or the data being
> read from it) is corrupt.

So how come it got corrupt? I did a 'dd if=/dev/zero of=/dev/sdb' (and
waited for the whole disk to be zeroed - took HOURS! :). Then partitioned
the disk and cut-and-pasted the output into the mail...

EVERY time I check the partition table (using mac-fdisk and not cfdisk),
that destorted output is shown. It's not distorted/corrupt if I use
cfdisk though...


Since I don't exactly know how to do all this with the tools in Linux,
I took the disk to my girlfriends WinXP and is currently using
'OnTrack EasyRecorvery Professional - ERP' to do scanns and tests of
the disk.

I tried parition and format it there to, but the format failed (no reason
why). I'm currently running the extended S.M.A.R.T. test. And there where
other tests I could do to... I'll let you know.
One weird thing though... ERP only found it as a 137Mb disk! It's supposed
to be a 400Gb...
-- 
Ft. Bragg ammonium genetic Ortega Nazi Uzi FSF Cocaine North Korea
Cuba Delta Force Qaddafi Treasury kibo Marxist
[See http://www.aclu.org/echelonwatch/index.html for more about this]
[Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf]
If neither of these works, try http://www.aclu.org and search for echelon.
Note. This is a real, not fiction.
http://www.theregister.co.uk/2001/09/06/eu_releases_echelon_spying_report/
http://www.aclu.org/safefree/nsaspying/23989res20060131.html#echelon
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Weird harddisk behaviour

[Turbo Fredriksson]

when there is no longer anything to take away.
   -- Antoine de Saint-Exupery
Date: Sat, 20 Jan 2007 20:58:17 +0100
In-Reply-To: [EMAIL PROTECTED] (Ken Moffat's message of
 Thu, 18 Jan 2007 00:18:38 +)
Message-ID: [EMAIL PROTECTED]
User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/20.7 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Quoting Ken Moffat [EMAIL PROTECTED]:

  So, you were using a valid tool, but what you put in your original
 mail shows garbage - something like apple_partition_ma[mamama...

That's what fdisk showed me. I don't have a true UTF-8 system, so when
cutting-and-pasing between the shell and mail app, it might have been
distorted. But the output WAS weird!

 But if it isn't, somehow the data on the disk (or the data being
 read from it) is corrupt.

So how come it got corrupt? I did a 'dd if=/dev/zero of=/dev/sdb' (and
waited for the whole disk to be zeroed - took HOURS! :). Then partitioned
the disk and cut-and-pasted the output into the mail...

EVERY time I check the partition table (using mac-fdisk and not cfdisk),
that destorted output is shown. It's not distorted/corrupt if I use
cfdisk though...


Since I don't exactly know how to do all this with the tools in Linux,
I took the disk to my girlfriends WinXP and is currently using
'OnTrack EasyRecorvery Professional - ERP' to do scanns and tests of
the disk.

I tried parition and format it there to, but the format failed (no reason
why). I'm currently running the extended S.M.A.R.T. test. And there where
other tests I could do to... I'll let you know.
One weird thing though... ERP only found it as a 137Mb disk! It's supposed
to be a 400Gb...
-- 
Ft. Bragg ammonium genetic Ortega Nazi Uzi FSF Cocaine North Korea
Cuba Delta Force Qaddafi Treasury kibo Marxist
[See http://www.aclu.org/echelonwatch/index.html for more about this]
[Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf]
If neither of these works, try http://www.aclu.org and search for echelon.
Note. This is a real, not fiction.
http://www.theregister.co.uk/2001/09/06/eu_releases_echelon_spying_report/
http://www.aclu.org/safefree/nsaspying/23989res20060131.html#echelon
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Weird harddisk behaviour

[Turbo Fredriksson]

Quoting Ken Moffat <[EMAIL PROTECTED]>:

> On Tue, Jan 16, 2007 at 02:27:06PM +0100, Turbo Fredriksson wrote:
>> A couple of weeks ago my 400Gb SATA disk crashed. I just
>> got the replacement, but I can't seem to be able to create
>> a filesystem on it!
>> 
>> This is a PPC (Pegasos), running 2.6.15-27-powerpc (Ubuntu Dapper 
>> v2.6.15-27.50).
> Hi Turbo,
>
>  I think you have mac partitions (the first item is the partition
> map itself - very different from the dos partitions common on x86).
>
>  Certainly, fdisk from util-linux doesn't know about mac disks, and
> I thought the same was true for cfdisk and sfdisk.  Many years ago
> there was mac-fdisk, I think also known as pdisk, but nowadays the
> common tool for partitioning mac disks is probably parted.

Yes. See now that 'fdisk' is a softlink to 'mac-fdisk'...

> Please try parted.

Same thing ('mkpartfs primary ext2 0 40'):

Jan 17 11:03:41 localhost kernel: [254985.117447] EXT2-fs: sdb1: couldn't mount 
RDWR because of unsupported optional features (1).


The 'unsupported optional features' number keeps changing... ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Weird harddisk behaviour

[Turbo Fredriksson]

Quoting Ken Moffat [EMAIL PROTECTED]:

 On Tue, Jan 16, 2007 at 02:27:06PM +0100, Turbo Fredriksson wrote:
 A couple of weeks ago my 400Gb SATA disk crashed. I just
 got the replacement, but I can't seem to be able to create
 a filesystem on it!
 
 This is a PPC (Pegasos), running 2.6.15-27-powerpc (Ubuntu Dapper 
 v2.6.15-27.50).
 Hi Turbo,

  I think you have mac partitions (the first item is the partition
 map itself - very different from the dos partitions common on x86).

  Certainly, fdisk from util-linux doesn't know about mac disks, and
 I thought the same was true for cfdisk and sfdisk.  Many years ago
 there was mac-fdisk, I think also known as pdisk, but nowadays the
 common tool for partitioning mac disks is probably parted.

Yes. See now that 'fdisk' is a softlink to 'mac-fdisk'...

 Please try parted.

Same thing ('mkpartfs primary ext2 0 40'):

Jan 17 11:03:41 localhost kernel: [254985.117447] EXT2-fs: sdb1: couldn't mount 
RDWR because of unsupported optional features (1).


The 'unsupported optional features' number keeps changing... ?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Weird harddisk behaviour

[Turbo Fredriksson]

A couple of weeks ago my 400Gb SATA disk crashed. I just
got the replacement, but I can't seem to be able to create
a filesystem on it!

This is a PPC (Pegasos), running 2.6.15-27-powerpc (Ubuntu Dapper 
v2.6.15-27.50).

- s n i p -
[EMAIL PROTECTED]:~# cfdisk -P s /dev/sda
Partition Table for /dev/sda

   First   Last
 # Type   Sector  Sector   OffsetLength   Filesystem Type (ID) Flag
-- --- --- --- -- ---  
 1 Primary   0   781417664 63   781417665 Linux raid auto (FD) None
[EMAIL PROTECTED]:~# cfdisk -P s /dev/sdb
Partition Table for /dev/sdb

   First   Last
 # Type   Sector  Sector   OffsetLength   Filesystem Type (ID) Flag
-- --- --- --- -- ---  
 1 Primary   0   781417664 63   781417665 Linux raid auto (FD) None
[EMAIL PROTECTED]:~# mke2fs -v -j /dev/sdb1
mke2fs 1.38 (30-Jun-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
48840704 inodes, 97677200 blocks
4883860 blocks (5.00%) reserved for the super user
First data block=0
2981 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
[EMAIL PROTECTED]:~# e2fsck /dev/sdb1
e2fsck 1.38 (30-Jun-2005)
e2fsck: Filesystem revision too high while trying to open /dev/sdb1
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)


The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 

[EMAIL PROTECTED]:~# mount /dev/sdb1 /mnt/sdb
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
   missing codepage or other error
   In some cases useful info is found in syslog - try
   dmesg | tail  or so

[EMAIL PROTECTED]:~# dmesg | tail -n1
[154695.371073] EXT3-fs: sdb1: couldn't mount because of unsupported optional 
features (2).
- s n i p -

I tried using fdisk instead. Note that fdisk finds a different
partition table than cfdisk above!

- s n i p -
[EMAIL PROTECTED]:~# fdisk -l /dev/sdb
/dev/sdb
#type name  length   base  ( 
size )  system
/dev/sdb1Apple_partitiooma}amamamamamama Apple 63 @ 1   
  ( 31.5k)  Unknown
/dev/sdb2Apple_gee_e_e_e_e_e_ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL 
PROTECTED]@.%G�%@ 781434611 @ 781397715 (372.6G)  Unknown

Block size=512, Number of Blocks=781422768
DeviceType=0x0, DeviceId=0x0

[EMAIL PROTECTED]:~# dd if=/dev/zero of=/dev/sdb count=1
1+0 records in
1+0 records out
512 bytes (5.1 MB) copied, 0.366181 seconds, 14.0 MB/s
[EMAIL PROTECTED]:~# fdisk -l /dev/sdb
[EMAIL PROTECTED]:~# cfdisk -P s /dev/sdb
FATAL ERROR: No partition table.

=> [fdisk /dev/sdb and chooses 'initialize partition map'] <=
[EMAIL PROTECTED]:~# fdisk -l /dev/sdb
/dev/sdb
#type name  length   base  ( 
size )  system
/dev/sdb1Apple_partitmooma}amamamamamama Apple 63 @ 1   
  ( 31.5k)  Unknown
/dev/sdb2Apple_gee_e_e_e_e_e_ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL 
PROTECTED]@.%G�%@ 781434611 @ 781397715 (372.6G)  Unknown

Block size=512, Number of Blocks=781422768
DeviceType=0x0, DeviceId=0x0

[EMAIL PROTECTED]:~# cfdisk -P s /dev/sdb
FATAL ERROR: No partition table.

=> [fdisk /dev/sdb and deletes both partitions (!!)] <=
[EMAIL PROTECTED]:~# fdisk -l /dev/sdb
/dev/sdb
#type name  length   base  ( 
size )  system
/dev/sdb1  Apple_Free Extra 63 @ 1 ( 
31.5k)  Free space
/dev/sdb2Apple_gee_e_e_e_e_e_ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL 
PROTECTED]@.%G�%@ 781434611 @ 781397715 (372.6G)  Unknown

Block size=512, Number of Blocks=781422768
DeviceType=0x0, DeviceId=0x0

=> [in the syslog during the fdisk sessions:] <=
[EMAIL PROTECTED]:~# tail -f /var/log/syslog -n0
Jan 16 07:15:59 localhost kernel: [154926.816696] SCSI device sdb: 781422768 
512-byte hdwr sectors (400088 MB)
Jan 16 07:15:59 localhost kernel: [154926.817340] SCSI device sdb: drive cache: 
write back
Jan 16 07:15:59 localhost kernel: 

Weird harddisk behaviour

[Turbo Fredriksson]

A couple of weeks ago my 400Gb SATA disk crashed. I just
got the replacement, but I can't seem to be able to create
a filesystem on it!

This is a PPC (Pegasos), running 2.6.15-27-powerpc (Ubuntu Dapper 
v2.6.15-27.50).

- s n i p -
[EMAIL PROTECTED]:~# cfdisk -P s /dev/sda
Partition Table for /dev/sda

   First   Last
 # Type   Sector  Sector   OffsetLength   Filesystem Type (ID) Flag
-- --- --- --- -- ---  
 1 Primary   0   781417664 63   781417665 Linux raid auto (FD) None
[EMAIL PROTECTED]:~# cfdisk -P s /dev/sdb
Partition Table for /dev/sdb

   First   Last
 # Type   Sector  Sector   OffsetLength   Filesystem Type (ID) Flag
-- --- --- --- -- ---  
 1 Primary   0   781417664 63   781417665 Linux raid auto (FD) None
[EMAIL PROTECTED]:~# mke2fs -v -j /dev/sdb1
mke2fs 1.38 (30-Jun-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
48840704 inodes, 97677200 blocks
4883860 blocks (5.00%) reserved for the super user
First data block=0
2981 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
[EMAIL PROTECTED]:~# e2fsck /dev/sdb1
e2fsck 1.38 (30-Jun-2005)
e2fsck: Filesystem revision too high while trying to open /dev/sdb1
The filesystem revision is apparently too high for this version of e2fsck.
(Or the filesystem superblock is corrupt)


The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 device

[EMAIL PROTECTED]:~# mount /dev/sdb1 /mnt/sdb
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
   missing codepage or other error
   In some cases useful info is found in syslog - try
   dmesg | tail  or so

[EMAIL PROTECTED]:~# dmesg | tail -n1
[154695.371073] EXT3-fs: sdb1: couldn't mount because of unsupported optional 
features (2).
- s n i p -

I tried using fdisk instead. Note that fdisk finds a different
partition table than cfdisk above!

- s n i p -
[EMAIL PROTECTED]:~# fdisk -l /dev/sdb
/dev/sdb
#type name  length   base  ( 
size )  system
/dev/sdb1Apple_partitiooma}amamamamamama Apple 63 @ 1   
  ( 31.5k)  Unknown
/dev/sdb2Apple_gee_e_e_e_e_e_ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL 
PROTECTED]@.%G�%@ 781434611 @ 781397715 (372.6G)  Unknown

Block size=512, Number of Blocks=781422768
DeviceType=0x0, DeviceId=0x0

[EMAIL PROTECTED]:~# dd if=/dev/zero of=/dev/sdb count=1
1+0 records in
1+0 records out
512 bytes (5.1 MB) copied, 0.366181 seconds, 14.0 MB/s
[EMAIL PROTECTED]:~# fdisk -l /dev/sdb
[EMAIL PROTECTED]:~# cfdisk -P s /dev/sdb
FATAL ERROR: No partition table.

= [fdisk /dev/sdb and chooses 'initialize partition map'] =
[EMAIL PROTECTED]:~# fdisk -l /dev/sdb
/dev/sdb
#type name  length   base  ( 
size )  system
/dev/sdb1Apple_partitmooma}amamamamamama Apple 63 @ 1   
  ( 31.5k)  Unknown
/dev/sdb2Apple_gee_e_e_e_e_e_ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL 
PROTECTED]@.%G�%@ 781434611 @ 781397715 (372.6G)  Unknown

Block size=512, Number of Blocks=781422768
DeviceType=0x0, DeviceId=0x0

[EMAIL PROTECTED]:~# cfdisk -P s /dev/sdb
FATAL ERROR: No partition table.

= [fdisk /dev/sdb and deletes both partitions (!!)] =
[EMAIL PROTECTED]:~# fdisk -l /dev/sdb
/dev/sdb
#type name  length   base  ( 
size )  system
/dev/sdb1  Apple_Free Extra 63 @ 1 ( 
31.5k)  Free space
/dev/sdb2Apple_gee_e_e_e_e_e_ [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL 
PROTECTED]@.%G�%@ 781434611 @ 781397715 (372.6G)  Unknown

Block size=512, Number of Blocks=781422768
DeviceType=0x0, DeviceId=0x0

= [in the syslog during the fdisk sessions:] =
[EMAIL PROTECTED]:~# tail -f /var/log/syslog -n0
Jan 16 07:15:59 localhost kernel: [154926.816696] SCSI device sdb: 781422768 
512-byte hdwr sectors (400088 MB)
Jan 16 07:15:59 localhost kernel: [154926.817340] SCSI device sdb: drive cache: 
write back
Jan 16 07:15:59 localhost kernel: 

Compile fails on SPARC64 - include/linux/sched.h:1171: request for member `break_lock' in something not a structure or union

[Turbo Fredriksson]

Tried 2.6.11.6, 2.6.11.6-bk1 and 2.6.12-rc1.

- s n i p -
CHROOT Aurora/Woody-devel# make
  CHK include/linux/version.h
  CC  init/main.o
In file included from include/linux/module.h:10,
 from init/main.c:16:
include/linux/sched.h: In function `lock_need_resched':
include/linux/sched.h:1171: request for member `break_lock' in something not a 
structure or union
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2
- s n i p -

rgrep'ing in include/ shows that it's defined in all
but 'include/asm-sparc64/spinlock.h':

- s n i p -
CHROOT Aurora/Woody-devel# rgrep break_lock include | sort | uniq
include/asm-alpha/spinlock.h:   unsigned int break_lock;
include/asm-arm/spinlock.h: unsigned int break_lock;
include/asm-i386/spinlock.h:unsigned int break_lock;
include/asm-ia64/spinlock.h:unsigned int break_lock;
include/asm-m32r/spinlock.h:unsigned int break_lock;
include/asm-mips/spinlock.h:unsigned int break_lock;
include/asm-parisc/spinlock.h:  unsigned int break_lock;
include/asm-parisc/system.h:unsigned int break_lock;
include/asm-ppc/spinlock.h: unsigned int break_lock;
include/asm-ppc64/spinlock.h:   unsigned int break_lock;
include/asm-s390/spinlock.h:unsigned int break_lock;
include/asm-sh/spinlock.h:  unsigned int break_lock;
include/asm-sparc/spinlock.h:   unsigned int break_lock;
include/asm-x86_64/spinlock.h:  unsigned int break_lock;
include/linux/sched.h:# define need_lockbreak(lock) ((lock)->break_lock)
- s n i p -

Kernel config can be found at http://www.bayour.com/config-2.6.12-rc1.txt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Compile fails on SPARC64 - include/linux/sched.h:1171: request for member `break_lock' in something not a structure or union

[Turbo Fredriksson]

Tried 2.6.11.6, 2.6.11.6-bk1 and 2.6.12-rc1.

- s n i p -
CHROOT Aurora/Woody-devel# make
  CHK include/linux/version.h
  CC  init/main.o
In file included from include/linux/module.h:10,
 from init/main.c:16:
include/linux/sched.h: In function `lock_need_resched':
include/linux/sched.h:1171: request for member `break_lock' in something not a 
structure or union
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2
- s n i p -

rgrep'ing in include/ shows that it's defined in all
but 'include/asm-sparc64/spinlock.h':

- s n i p -
CHROOT Aurora/Woody-devel# rgrep break_lock include | sort | uniq
include/asm-alpha/spinlock.h:   unsigned int break_lock;
include/asm-arm/spinlock.h: unsigned int break_lock;
include/asm-i386/spinlock.h:unsigned int break_lock;
include/asm-ia64/spinlock.h:unsigned int break_lock;
include/asm-m32r/spinlock.h:unsigned int break_lock;
include/asm-mips/spinlock.h:unsigned int break_lock;
include/asm-parisc/spinlock.h:  unsigned int break_lock;
include/asm-parisc/system.h:unsigned int break_lock;
include/asm-ppc/spinlock.h: unsigned int break_lock;
include/asm-ppc64/spinlock.h:   unsigned int break_lock;
include/asm-s390/spinlock.h:unsigned int break_lock;
include/asm-sh/spinlock.h:  unsigned int break_lock;
include/asm-sparc/spinlock.h:   unsigned int break_lock;
include/asm-x86_64/spinlock.h:  unsigned int break_lock;
include/linux/sched.h:# define need_lockbreak(lock) ((lock)-break_lock)
- s n i p -

Kernel config can be found at http://www.bayour.com/config-2.6.12-rc1.txt.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/