Something is happening to stop me accessing my /home/john directory as user.
Using Krusader, for example, as su Krusader I can access all my files. As user Krusader crashes if I try to access /home/john.
The same applies to other programs that try to access /home/john - e.g. Gwenview.
Using 11.1RC1 and had the kernel upgrade this morning.
Is your /home on a separate partition?
Check the rights for /home and your user directory…
~>ls / -al | grep home
drwxr-xr-x 3 root root 72 2008-11-28 09:08 home
~>ls /home -al
total 2
drwxr-xr-x 3 root root 72 2008-11-28 09:08 .
drwxr-xr-x 23 root root 536 2008-12-06 18:44 …
drwxr-xr-x 39 <user> users 1752 2008-12-06 18:45 <user>
also make sure, if using a separate partition for /home, that it’s not mount read-only. you can check this with ’ mount ’
Thanks for the reply - I was hoping someone would say “Oh yes, this is happening now because…” 
Yes, /home is in a separate partition. My outputs were the same as yours. Mount shows rw.
The first time this happened this morning I was changing the permissions in a /home directory. Fortunately, it was a CVS directory I was able to delete entirely using terminal and that solved the problem.
This afternoon, I edited a .jpg with gimp and saved it to a different directory. I opened Quanta which could not access /Home. I then found Krusader crashed trying to access /Home/John. I deleted the directory with the new .jpg in it - no joy. I have copied the original directory to another disk using Krusader as SU and deleted the original. But this also has had no effect.
hmmm… which filetype does your home partition have?
There are some reports on the new update (yesterday/today) causing issues booting… could be related?
See here for one thread… RC1 system broken after auto update of kernel - openSUSE Forums
I’ve not had any issues (so far).
Ext3
Dolphin is user mode states there are no files in /home/john
In Krusader, user mode, clicking on home brings up john and “lost and found” directories. Clicking on john crashes it.
Using ext3 here for home too.
Not meant as a ‘shovein it off me’ comment… but it could be KDE 4.1 related? I’m running GNOME here without much hassle.
You could check which packages got updated and revert to the previous versions.
As I user zypper to update, the history is in /var/log/zypper
Don’t know if the updater applet uses zypper as backend in 11.1.
Interesting - rebooted and things are Ok again, although I was removing directories one by one before to see if that had any effect. Rebooting this morning did not solve the problem.
On close down, unmounting fuse file control failed and then there was another unmounting failure - something to do with locking, but it then closed down too quickly for me to read it.
Tomorrow, I’ll add back the directories one by one and see if any of them causes the problem again.
Thanks again for the help
You might find those errors in /var/log/messages or /var/log/warn
To quickly find the bits around your last shutdown(s), open /var/log/messages and search from end up for : Kernel log daemon terminating
No problem… that’s what the forums are for
Cheers,
Wj
i have the same problem -> Firefox “unmounts” my user home folder - openSUSE Forums
only when i start firefox the issue comes to bring me pain :P, right now i have to browse the Internet with konqueror.
kernel upgrade = Probably fstab didn’t get written properly here’s my line with /home:
/etc/fstab
/dev/disk/by-id/ata-ST3500320AS_9QM5PXG3-part2 /home ext3 acl,user_xattr 1 2
Works for me.
edit your’s, save, reboot
i have only one partition (/)
/dev/disk/by-id/ata-Maxtor_6Y080L0_Y2P29XRE-part1 / reiserfs acl,user_xattr 1 1
/dev/disk/by-id/ata-Maxtor_6L080L0_L224A7CH-part2 swap swap defaults 0 0
/dev/disk/by-id/ata-Maxtor_6L080L0_L224A7CH-part1 /respaldo reiserfs user,acl 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
is that ok ??
Greetings !!
Yes but, I really recommend a separate /home partition as it makes it very easy to go from rc1 to GM (among a whole raft of other things like saving all your “stuff”).
I think when it is all in one partition /home is IDed by a symlink which should be written with the kernel install. Sorry, I don’t know it at the moment & not sure where to look – as I use a separate /home partition.
You could try forcing a kernel update “using the same version” in yast but using a different repo (like widehat.opensuse.org) & hopefully that symlink will get written.
Or, just update the kernel (but you want kernel-base, kernel-extra, kernel-source & kernel-syms to match).
Good luck:)
Nothing wrong in fstab.
System log stops before the mounting issues happens - I suppose it would, wouldn’t it - little point writing to a disk that’s being unmounted…
Oh well, things still working this morning.
Another /home issue and straight after using The Gimp, so it looks pretty conclusively that it is The Gimp that is causing the issue. Deleting the .gimp directory and rebooting resolves the issue.
I think I’ll simply downgrade the Gimp to an older version and lock it for a while.
Sounds more like your / is going read-only?
I did have one freeze a couple of days ago that I accounted to some other issue. But checking the logs backtracking to that moment, I encountered this:
Dec 4 10:47:07 OSUSE111 kernel: end_request: I/O error, dev sdb, sector 1482490600
Dec 4 10:47:07 OSUSE111 kernel: Buffer I/O error on device sdb2, logical block 1550
Dec 4 10:47:07 OSUSE111 kernel: lost page write due to I/O error on sdb2
Dec 4 10:47:07 OSUSE111 kernel: Aborting journal on device sdb2.
Dec 4 10:47:07 OSUSE111 kernel: Buffer I/O error on device sdb2, logical block 1545
Dec 4 10:47:07 OSUSE111 kernel: lost page write due to I/O error on sdb2
Dec 4 10:47:07 OSUSE111 kernel: journal commit I/O error
sdb is a usb disk I had attached…
At the time I was busy with a ssh session with X forwarding enabled… one of those things that normally never causes any issues.
Then last night when closing Firefox (it had some java related sites open), my X session froze… mouse was still moving, but keyboard input wasn’t accepted.
I could not even switch to a console using ALT-F1,2,3…
I’ve set my powermanagement (GNOME) to do a shutdown when pressing the power button… and that worked without any errors shown while shutting down.
The only possible error I found in the logs is:
Dec 6 22:15:39 OSUSE111 smartd[4080]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 3 Spin_Up_Time changed from 218 to 231
Dec 6 22:15:39 OSUSE111 smartd[4080]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 122 to 137
’ smartctl /dev/sda -a ’ indicates all should be fine (main values: status PASSED & no errors logged).
Or my disk is failing and this is a coincidence… or there is something fishy wish the new kernel and drive access or other?
(!) Not saying this is related to what you are experiencing, but just comparing notes and checking to exclude this as issue…
root and /home values in fstab:
/dev/disk/by-id/ata-Hitachi_HTS721080G9SA00_MPCD12Y4GL6BZE-part2 / reiserfs acl,user_xattr 1 1
/dev/disk/by-id/ata-Hitachi_HTS721080G9SA00_MPCD12Y4GL6BZE-part3 /home ext3 defaults 1 2
Why would that stop programs accessing the partition and actually crashing them? It seems that the partition is being changed to root access as su running programs can access the files. But I’m pretty hazy on all this stuff - learning though!
Hmmm, The Gimp has been removed but the problem has just occurred again, 
This is what /var/log/messages is reporting:
Dec 7 17:03:39 linux-wf9z -- MARK --
Dec 7 17:19:24 linux-wf9z kernel: usb 4-4: new high speed USB device using ehci_hcd and address 3
Dec 7 17:19:24 linux-wf9z kernel: usb 4-4: configuration #1 chosen from 1 choice
Dec 7 17:19:24 linux-wf9z kernel: usb 4-4: New USB device found, idVendor=04b0, idProduct=0411
Dec 7 17:19:24 linux-wf9z kernel: usb 4-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 7 17:19:24 linux-wf9z kernel: usb 4-4: Product: NIKON DSC D80
Dec 7 17:19:24 linux-wf9z kernel: usb 4-4: Manufacturer: NIKON
Dec 7 17:19:24 linux-wf9z kernel: usb 4-4: SerialNumber: 8038512
Dec 7 17:19:25 linux-wf9z kernel: Initializing USB Mass Storage driver...
Dec 7 17:19:25 linux-wf9z kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Dec 7 17:19:25 linux-wf9z kernel: usbcore: registered new interface driver usb-storage
Dec 7 17:19:25 linux-wf9z kernel: USB Mass Storage support registered.
Dec 7 17:19:25 linux-wf9z kernel: usb-storage: device found at 3
Dec 7 17:19:25 linux-wf9z kernel: usb-storage: waiting for device to settle before scanning
Dec 7 17:19:26 linux-wf9z kernel: scsi 2:0:0:0: Direct-Access NIKON D80 1.01 PQ: 0 ANSI: 2
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: [sdc] 4019200 512-byte hardware sectors: (2.05GB/1.91GiB)
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: [sdc] Write Protect is off
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: [sdc] Mode Sense: 0f 00 00 00
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: [sdc] 4019200 512-byte hardware sectors: (2.05GB/1.91GiB)
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: [sdc] Write Protect is off
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: [sdc] Mode Sense: 0f 00 00 00
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through
Dec 7 17:19:26 linux-wf9z kernel: sdc: sdc1
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk
Dec 7 17:19:26 linux-wf9z kernel: sd 2:0:0:0: Attached scsi generic sg3 type 0
Dec 7 17:19:26 linux-wf9z kernel: usb-storage: device scan complete
Dec 7 17:20:47 linux-wf9z su: (to root) john on /dev/pts/5
Dec 7 17:20:47 linux-wf9z su: (to root) john on /dev/pts/5
Dec 7 17:21:13 linux-wf9z kernel: usb 4-4: USB disconnect, address 3
Dec 7 17:21:32 linux-wf9z kernel: usb 4-4: new high speed USB device using ehci_hcd and address 4
Dec 7 17:21:33 linux-wf9z kernel: usb 4-4: configuration #1 chosen from 1 choice
Dec 7 17:21:33 linux-wf9z kernel: scsi3 : SCSI emulation for USB Mass Storage devices
Dec 7 17:21:33 linux-wf9z kernel: usb 4-4: New USB device found, idVendor=04b0, idProduct=0411
Dec 7 17:21:33 linux-wf9z kernel: usb 4-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 7 17:21:33 linux-wf9z kernel: usb 4-4: Product: NIKON DSC D80
Dec 7 17:21:33 linux-wf9z kernel: usb 4-4: Manufacturer: NIKON
Dec 7 17:21:33 linux-wf9z kernel: usb 4-4: SerialNumber: 8038512
Dec 7 17:21:33 linux-wf9z kernel: usb-storage: device found at 4
Dec 7 17:21:33 linux-wf9z kernel: usb-storage: waiting for device to settle before scanning
Dec 7 17:21:34 linux-wf9z kernel: scsi 3:0:0:0: Direct-Access NIKON D80 1.01 PQ: 0 ANSI: 2
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: [sdc] 4019200 512-byte hardware sectors: (2.05GB/1.91GiB)
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: [sdc] Write Protect is off
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: [sdc] Mode Sense: 0f 00 00 00
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: [sdc] Assuming drive cache: write through
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: [sdc] 4019200 512-byte hardware sectors: (2.05GB/1.91GiB)
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: [sdc] Write Protect is off
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: [sdc] Mode Sense: 0f 00 00 00
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: [sdc] Assuming drive cache: write through
Dec 7 17:21:34 linux-wf9z kernel: sdc: sdc1
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: [sdc] Attached SCSI removable disk
Dec 7 17:21:34 linux-wf9z kernel: sd 3:0:0:0: Attached scsi generic sg3 type 0
Dec 7 17:21:34 linux-wf9z kernel: usb-storage: device scan complete
Dec 7 17:22:27 linux-wf9z kernel: usb 4-4: USB disconnect, address 4
Dec 7 17:23:40 linux-wf9z syslog-ng[2037]: Log statistics; dropped='pipe(/dev/xconsole)=0',
dropped='pipe(/dev/tty10)=0',
processed='center(queued)=137',
processed='center(received)=112', processed='destination(newsnotice)=0',
processed='destination(acpid)=0', processed='destination(firewall)=0',
processed='destination(null)=0', processed='destination(mail)=6', processed='destination(mailinfo)=0',
processed='destination(console)=4',
processed='destination(newserr)=0',
processed='destination(newscrit)=0',
processed='destination(messages)=106',
processed='destination(mailwarn)=0', processed='destination(localmessages)=1',
processed='destination(netmgm)=0', processed='destination(mailerr)=6',
processed='destination(xconsole)=4',
processed='destination(warn)=10', processed='source(src)=112'
I have no idea what the
Dec 7 17:23:40 linux-wf9z syslog-ng[2037]: Log statistics; dropped='pipe(/dev/xconsole)=0',
dropped='pipe(/dev/tty10)=0',
processed='center(queued)=137',
is about… But there is nothing in that bit of log jumping out at me as an issue… Were you scanning something at that moment? If not, try disconnecting the scanner.
If you’ve done a fresh install of RC1 you still have the installation DVD/CD? You should be able to downgrade the kernel back to the version supplied with RC1.
For this insert your install source, open YaST > Software Management and search for installed packages with the keyword ’ kernel- ’
There you can downgrade all the mentioned kernel packages you see listed, revert them back to RC1 level and reboot to let it take effect.
Hope that helps…
Wj
ps. apart from the issue I posted all is still quite stable here… ?
i have re installed opensuse 11.1 rc1 again, then updated with default repositories (first i’ve removed debug repository), then added kde stable repos, packman, vlc and some other repos from the opensuse list and update again.
Now everything is working correctly.
Greetings !!
Downgrading the kernel is the obvious option, but I would like to get to the bottom of the issue.
After posting last night, I closed down the system. It failed to unmount fuse file system and also /home and /VolB (my second HD) saying they were “busy”.
I ran the repair system this morning and it reported a number of errors in sda2 - my root partition. It was unable to repair one which said - “inode 1297198 has imagic flag set - Unexpected inconsistency run fsck manually”.
I ran fsck which picked up several dozen issues. Rebooted and thing are all working again.
Thinking back, I changed some permissions in both /home and /VolB yesterday afternoon. It was after that the problems started again, so I am now thinking that is the cause.