Re: Network interface "stops working"

2018-01-23 Thread 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

Network interface "stops working"

2018-01-22 Thread 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

unmap/blacklist memory page?

2015-11-24 Thread 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

Re: Moving MD/LVM from PPC to x86

2007-07-11 Thread 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

Re: Moving MD/LVM from PPC to x86

2007-07-09 Thread 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. big

Re: Moving MD/LVM from PPC to x86

2007-07-08 Thread 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 -

Re: Moving MD/LVM from PPC to x86

2007-07-04 Thread 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 >

Re: Forcibly remove broken disk from LV

2007-07-04 Thread 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 remov

Re: Moving MD/LVM from PPC to x86

2007-06-30 Thread 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 disk

Moving MD/LVM from PPC to x86

2007-06-28 Thread 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 SA

Re: Weird harddisk behaviour

2007-01-20 Thread 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/

Re: Weird harddisk behaviour

2007-01-17 Thread 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! >>

Weird harddisk behaviour

2007-01-16 Thread 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

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

2005-03-28 Thread 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': in