| View previous topic :: View next topic |
| Author |
Message |
shprauff
n00b
Joined: 09 Dec 2005
Posts: 15
Location: France
|
 Posted: Mon Feb 25, 2008 11:11 am Post subject: Kernel upgrade weirdness [SOLVED] |
 |
|
Hello people of gentoo.
I have a weird problem of filesystem corruption happening with the latest hardened kernel (linux-hardened-2.6.23-r7).
Since the announcement of the vmsplice vulnerability I decided to upgrade the kernel of my servers currently running on linux-hardened-2.6.18-r6.
For now I only tried the upgrade on one of the servers (a Sun Fire X2100).
here is the fstab:
| Code: |
/dev/sda1 /boot ext3 noauto,noatime 1 2
/dev/sda2 / ext3 noatime 0 1
/dev/sda3 /usr ext3 noatime 0 2
/dev/sda5 /usr/portage ext3 noatime 0 2
/dev/sda6 none swap sw 0 0
/dev/sda7 /var ext3 noatime 0 2
/dev/sda9 /backup ext3 noatime 0 2
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
proc /proc proc defaults 0 0
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
|
I can post the kernel .config if necessary
I have a problem with /dev/sda7 , while booting on the old kernel, it can be mounted in read/write mode without any problems and the system is initialized properly.
But when I boot on my new kernel I get a "journal commit I/O Error" just after the "device initiated services" part.
/var gets mounted read-only and the system is unable to create necessary symlinks in /var in order to complete the boot sequence.
The thing is , that partition can be be mounted in read-write mode without any problems in the old kernel but not in the new one.
I ran S.M.A.R.T. tests, checked for badblocks, there is no errors reported (it's a SATA drive), so I thought it would be just a corrupted filesystem so I made a backup of /var and proceeded to reformat that specific partition and copy back the files
Here is the commands I used to format the partition (same as the other ones):
| Code: |
mke2fs -j -O dir_index /dev/sda7
tune2fs -o journal_data /dev/sda7
|
But even after that (despite being completely usable on 2.6.18-r6), I still have that problem while booting on the new kernel (journal commit I/O Error) and it corrupts the partition (according to fsck), /var gets mounted read-only and the problem continues.
I need enlightenment 
I have backups so I can easily reinstall.
What I find really weird is that it works flawlessly in one kernel but not in the other...
Last edited by shprauff on Tue Feb 26, 2008 9:42 am; edited 1 time in total |
|
| Back to top |
|
 |
jyaan
Tux's lil' helper
Joined: 24 Feb 2008
Posts: 79
Location: USA
|
| Posted: Mon Feb 25, 2008 1:17 pm Post subject: |
|
|
really weird.....
well, you've probably already tried this, but i'll mention it just in case:
id go ahead and open two terminal windows, each with and go through each level comparing side by side. it's happened to me before where ive left out some of the simplest things, and having the visual comparison may help hunt down something missed.
also, if you used one of the programs for copying over your kernel config data, this can lead to compatibility problems between versions. so id say open up in the 'good' kernel and try the above in either case.
aside from that, i really cant think of much. if this doesnt solve it then its probably a kernel bug you should report. |
|
| Back to top |
|
|
shprauff
n00b
Joined: 09 Dec 2005
Posts: 15
Location: France
|
| Posted: Mon Feb 25, 2008 1:50 pm Post subject: |
|
|
I'll try that, for now I used my old .config and worked from there in menuconfig.
I'm going to check the other partitions as well with a livecd just to be sure.
Going to check bios updates too, you never know. |
|
| Back to top |
|
|
jyaan
Tux's lil' helper
Joined: 24 Feb 2008
Posts: 79
Location: USA
|
| Posted: Mon Feb 25, 2008 1:53 pm Post subject: |
|
|
| good luck, let me know what happens |
|
| Back to top |
|
|
shprauff
n00b
Joined: 09 Dec 2005
Posts: 15
Location: France
|
| Posted: Tue Feb 26, 2008 9:42 am Post subject: |
|
|
Okay after checking the partitions (and I found nothing weird), I flashed the bios and now everything works 
Thanks for the help |
|
| Back to top |
|
|
Cyker
Veteran
Joined: 15 Jun 2006
Posts: 1130
|
| Posted: Tue Feb 26, 2008 11:34 am Post subject: |
|
|
The problem was caused by the BIOS?! 
Well caught... I'd never have thought of that! |
|
| Back to top |
|
|
shprauff
n00b
Joined: 09 Dec 2005
Posts: 15
Location: France
|
| Posted: Tue Feb 26, 2008 6:41 pm Post subject: |
|
|
| Yes it's weird, I wonder what changed in the kernel between those versions. |
|
| Back to top |
|
|
|
Kernel & Hardware
