On Thu, Dec 07, 2006 at 11:40:11PM -0500, Chuck wrote: > On Thursday 07 December 2006 23:33, Chuck wrote: > > also what version tools should i use with this? i currently have > > 0.30.211
0.30.212 would be fine ... best, Herbert > > On Thursday 07 December 2006 23:03, Herbert Poetzl wrote: > > > > 2.6.19 is now stable. this is still the proper patch? > > > > vs2.2.0-rc2 > > > > > > > On Thu, Dec 07, 2006 at 07:06:29PM -0500, Chuck wrote: > > > > On Thursday 07 December 2006 13:38, Herbert Poetzl wrote: > > > > > On Thu, Dec 07, 2006 at 08:57:41AM -0500, Chuck wrote: > > > > > > > > > > > > ok. i am definitely having problems with this new opteron machine > > > > > > we > > > > > > > > have... > > > > > > > > > > only thing i can see remotely close to an error or warning msg is > > > > > > this > > > > > > > > from > > > > > > > > > > the kernel: > > > > > > > > > > > > i get this message as early in the boot process as when it > > > > > > decompresses to begin boot: > > > > > > > > > > > > "kernel mapping table up to 100,000,000 at 8000:d800" > > > > > > > > > > that is the 'normal' bootup message you get on the > > > > > (VGA) console when the kernel boots and is either > > > > > set to quiet boot mode or has some other console > > > > > activated ... i.e. that is nothing unusual on x86_64 :) > > > > > > > > > oh ok. guess thats why it was not preceeded with warning or error or > > > > something. > > > > > > > > > > this is a linux 2.6.18.3 kernel > > > > > > > > > > > > 2.6.18-vs2.1.1-gentoo-r1 > > > > > > > > > > > > could this be a disk controller address? > > > > > > > > > > > > last week the machine died twice both with disk errors, the 2nd > > > > > > time it actually scrambled a few sectors in a lvm partition in the > > > > > > website vserver. i had to run shred on the partition to fix it. > > > > > > > > > > it seems there were some issues with certain block I/O > > > > > and/or filesystems, but they should be fixed in 2.6.18.5 > > > > > and later > > > > > > > > > > > > > maybe i did not update kernel high enough then. i went from 2.6.18.2 to > > > > 2.6.18.3 > > > > > > > > > > > > maybe ill just bite the bullet and get the 2.6.19 release from > > > > kernel.org. > > > > > > > > is there a vserver patch for that yet? also for 18.5? > > > > > > > > will search the site for the patches. > > > > > > yes, all there ... > > > > > > > > > just this morning, initially i had no warning something was wrong > > > > > > until i tried to execute any command and got back 'command not > found'. > > > > > > turns out the running system could not access the disk array in any > > > > > > fashion. a power cycle brought it back to normal and it has been > > > > > > running ok for the past few hours. > > > > > > > > > > that looks more like a faulty I/O subsystem ... maybe > > > > > a loose cable or interference with the bus subsystem > > > > > or just faulty disks ... > > > > > > > > will have the boss go back over there and double check everything > > > > again. he said last week when he looked every wire was harnessed and > > > > suspended around the sides of the case then came in to where they > > > > connected so nothing was laying on top of anything. > > > > > > double checking that won't hurt ... > > > > > > best, > > > Herbert > > > > > > > > > in case it helps > > > > > > hardware is > > > > > > 2xopteron dual core 265 > > > > > > tyan 2882D motherboard > > > > > > 4gb registered ram > > > > > > 2 sata2 drives in raid1 configuration. > > > > > > > > > > > > could i have a setting wrong in the kernel? > > > > > > > > > > maybe that for the console ... > > > > > > > > > > HTH, > > > > > Herbert > > > > > > > > > > > -- > > > > > > > > > > > > Chuck > > > > > > > > > > > > "...and the hordes of M$*ft users descended upon me in their anger, > > > > > > and asked 'Why do you not get the viruses or the BlueScreensOfDeath > > > > > > or insecure system troubles and slowness or pay through the nose > > > > > > for an OS as *we* do?!!', and I answered...'I use Linux'. " > > > > > > The Book of John, chapter 1, page 1, and end of book > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Vserver mailing list > > > > > > Vserver@list.linux-vserver.org > > > > > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > > > > > > > > > > -- > > > > > > > > Chuck > > > > > > > > "...and the hordes of M$*ft users descended upon me in their anger, > > > > and asked 'Why do you not get the viruses or the BlueScreensOfDeath > > > > or insecure system troubles and slowness or pay through the nose > > > > for an OS as *we* do?!!', and I answered...'I use Linux'. " > > > > The Book of John, chapter 1, page 1, and end of book > > > > > > > > > > > > _______________________________________________ > > > > Vserver mailing list > > > > Vserver@list.linux-vserver.org > > > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > > > > -- > > > > Chuck > > > > "...and the hordes of M$*ft users descended upon me in their anger, > > and asked 'Why do you not get the viruses or the BlueScreensOfDeath > > or insecure system troubles and slowness or pay through the nose > > for an OS as *we* do?!!', and I answered...'I use Linux'. " > > The Book of John, chapter 1, page 1, and end of book > > > > > > _______________________________________________ > > Vserver mailing list > > Vserver@list.linux-vserver.org > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > -- > > Chuck > > "...and the hordes of M$*ft users descended upon me in their anger, > and asked 'Why do you not get the viruses or the BlueScreensOfDeath > or insecure system troubles and slowness or pay through the nose > for an OS as *we* do?!!', and I answered...'I use Linux'. " > The Book of John, chapter 1, page 1, and end of book > > > _______________________________________________ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
