You are not logged in.
- Topics: Active | Unanswered
#1 2012-06-26 18:46:48
- Seninha
- Member
- From: Brasília - Brasil
- Registered: 2012-04-05
- Posts: 14
Partition becames read-only when login to user
My user's directory isn`t in '/home', it is in a partition that I mounted in '/media/Lucas'
Today, while my system was starting, appears a lot of errors (most of amsn, that can't save a file in ~/.cache)
What happens is that the partition becomes read-only
Then, I tried to investigate the problem:
* The user's permissions are the same that ever was. My user is the owner and all directories have permission of read and write
* I loged off my user and umounted the partition
* I mounted it again, and it keeps read-and-write as normal
* When I loged into my user again, the partition suddenly becomes read-only
1 - The pacman's log (/var/log/pacman.log)
[2012-06-25 13:04] Running 'pacman -Sy'
[2012-06-25 13:04] synchronizing package lists
[2012-06-25 14:05] Running 'pacman -Sy'
[2012-06-25 14:05] synchronizing package lists
[2012-06-25 15:06] Running 'pacman -Sy'
[2012-06-25 15:06] synchronizing package lists
[2012-06-25 16:07] Running 'pacman -Sy'
[2012-06-25 16:07] synchronizing package lists
[2012-06-25 17:08] Running 'pacman -Sy'
[2012-06-25 17:08] synchronizing package lists
[2012-06-25 18:09] Running 'pacman -Sy'
[2012-06-25 18:09] synchronizing package lists
[2012-06-25 19:09] Running 'pacman -Sy'
[2012-06-25 19:09] synchronizing package lists
[2012-06-25 19:53] Running 'pacman-color -S extra/sane community/simple-scan'
[2012-06-25 19:54] upgraded sane (1.0.22-9 -> 1.0.22-9)
[2012-06-25 19:54] upgraded simple-scan (3.4.1-1 -> 3.4.1-1)
[2012-06-25 20:10] Running 'pacman -Sy'
[2012-06-25 20:10] synchronizing package lists
[2012-06-25 21:11] Running 'pacman -Sy'
[2012-06-25 21:11] synchronizing package lists
[2012-06-25 22:12] Running 'pacman -Sy'
[2012-06-25 22:12] synchronizing package lists
[2012-06-25 23:13] Running 'pacman -Sy'
[2012-06-25 23:13] synchronizing package lists
[2012-06-26 13:15] Running 'pacman -Sy'
[2012-06-26 13:15] synchronizing package lists
[2012-06-26 13:21] Running 'pacman -Sy'
[2012-06-26 13:21] synchronizing package lists
[2012-06-26 13:43] Running 'pacman -Sy'
[2012-06-26 13:43] synchronizing package lists
[2012-06-26 13:56] Running 'pacman-color -R sane simple-scan'
[2012-06-26 13:57] Running 'pacman-color -Rcs sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -R sane'
[2012-06-26 13:58] Running 'pacman-color -R sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -R --debug sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -R --deps sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -Rd sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -R --nodeps sane simple-scan'
[2012-06-26 14:03] Running 'pacman-color -R initscripts'
[2012-06-26 14:03] warning: /etc/rc.local saved as /etc/rc.local.pacsave
[2012-06-26 14:03] warning: /etc/rc.conf saved as /etc/rc.conf.pacsave
[2012-06-26 14:03] warning: /etc/inittab saved as /etc/inittab.pacsave
[2012-06-26 14:03] removed initscripts (2012.06.1-1)
[2012-06-26 14:05] Running 'pacman-color -S core/initscripts'
[2012-06-26 14:05] installed initscripts (2012.06.1-1)
[2012-06-26 14:22] Running 'pacman -Sy'
[2012-06-26 14:22] synchronizing package lists2 - my /etc/fstab file:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# DEVICE DETAILS: /dev/sda2 UUID=ab0d2af5-7f13-43e1-a6c3-750a7eb3c172 LABEL=ARCH
# DEVICE DETAILS: /dev/sda3 UUID=fa2d57f0-a3f9-4309-b176-9b5ba8d6589c LABEL=SWAP
UUID=ab0d2af5-7f13-43e1-a6c3-750a7eb3c172 / ext4 defaults 0 1
UUID=fa2d57f0-a3f9-4309-b176-9b5ba8d6589c swap swap defaults 0 0
/dev/sda4 /media/Lucas reiserfs defaults,rw,user,exec,auto 0 0Last edited by Seninha (2012-06-26 19:03:18)
Offline
#2 2012-06-27 10:34:29
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,877
Re: Partition becames read-only when login to user
I see many pacman -Sy statements, but no pacman -Syu .
When was your last full update ?
Could you post the part of pacman.log from your last full update until now ?
Last edited by Lone_Wolf (2012-06-27 10:34:38)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#3 2012-06-27 19:24:33
- Seninha
- Member
- From: Brasília - Brasil
- Registered: 2012-04-05
- Posts: 14
Re: Partition becames read-only when login to user
I made a full update today.
There's many pacman -Sy statements because pacman write one "-Sy" for each repository that is checked for update in database.
Here's my complete pacman.log from 2012-06-25 until 2012-06-27 (today)
[2012-06-25 13:04] Running 'pacman -Sy'
[2012-06-25 13:04] synchronizing package lists
[2012-06-25 14:05] Running 'pacman -Sy'
[2012-06-25 14:05] synchronizing package lists
[2012-06-25 15:06] Running 'pacman -Sy'
[2012-06-25 15:06] synchronizing package lists
[2012-06-25 16:07] Running 'pacman -Sy'
[2012-06-25 16:07] synchronizing package lists
[2012-06-25 17:08] Running 'pacman -Sy'
[2012-06-25 17:08] synchronizing package lists
[2012-06-25 18:09] Running 'pacman -Sy'
[2012-06-25 18:09] synchronizing package lists
[2012-06-25 19:09] Running 'pacman -Sy'
[2012-06-25 19:09] synchronizing package lists
[2012-06-25 19:53] Running 'pacman-color -S extra/sane community/simple-scan'
[2012-06-25 19:54] upgraded sane (1.0.22-9 -> 1.0.22-9)
[2012-06-25 19:54] upgraded simple-scan (3.4.1-1 -> 3.4.1-1)
[2012-06-25 20:10] Running 'pacman -Sy'
[2012-06-25 20:10] synchronizing package lists
[2012-06-25 21:11] Running 'pacman -Sy'
[2012-06-25 21:11] synchronizing package lists
[2012-06-25 22:12] Running 'pacman -Sy'
[2012-06-25 22:12] synchronizing package lists
[2012-06-25 23:13] Running 'pacman -Sy'
[2012-06-25 23:13] synchronizing package lists
[2012-06-26 13:15] Running 'pacman -Sy'
[2012-06-26 13:15] synchronizing package lists
[2012-06-26 13:21] Running 'pacman -Sy'
[2012-06-26 13:21] synchronizing package lists
[2012-06-26 13:43] Running 'pacman -Sy'
[2012-06-26 13:43] synchronizing package lists
[2012-06-26 13:56] Running 'pacman-color -R sane simple-scan'
[2012-06-26 13:57] Running 'pacman-color -Rcs sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -R sane'
[2012-06-26 13:58] Running 'pacman-color -R sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -R --debug sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -R --deps sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -Rd sane simple-scan'
[2012-06-26 13:58] Running 'pacman-color -R --nodeps sane simple-scan'
[2012-06-26 14:03] Running 'pacman-color -R initscripts'
[2012-06-26 14:03] warning: /etc/rc.local saved as /etc/rc.local.pacsave
[2012-06-26 14:03] warning: /etc/rc.conf saved as /etc/rc.conf.pacsave
[2012-06-26 14:03] warning: /etc/inittab saved as /etc/inittab.pacsave
[2012-06-26 14:03] removed initscripts (2012.06.1-1)
[2012-06-26 14:05] Running 'pacman-color -S core/initscripts'
[2012-06-26 14:05] installed initscripts (2012.06.1-1)
[2012-06-26 14:22] Running 'pacman -Sy'
[2012-06-26 14:22] synchronizing package lists
[2012-06-26 15:24] Running 'pacman -Sy'
[2012-06-26 15:24] synchronizing package lists
[2012-06-26 15:58] Running 'pacman -Sy'
[2012-06-26 15:58] synchronizing package lists
[2012-06-26 16:51] Running 'pacman -Sy'
[2012-06-26 16:51] synchronizing package lists
[2012-06-26 16:56] Running 'pacman-color -R zeitgeist'
[2012-06-26 16:56] removed zeitgeist (0.9.0.1-1)
[2012-06-26 16:56] Running 'pacman-color -R -'
[2012-06-26 16:56] removed xapian-core (1.2.10-1)
[2012-06-26 16:56] removed box2d (2.2.1-2)
[2012-06-26 17:20] Running 'pacman-color -S core/sysvinit core/initscripts'
[2012-06-26 17:20] upgraded sysvinit (2.88-3 -> 2.88-3)
[2012-06-26 17:20] upgraded initscripts (2012.06.1-1 -> 2012.06.1-1)
[2012-06-26 17:22] Running 'pacman -Sy'
[2012-06-26 17:22] synchronizing package lists
[2012-06-26 17:28] Running 'pacman-color -R gvfs'
[2012-06-26 18:49] Running 'pacman -Sy'
[2012-06-26 18:49] synchronizing package lists
[2012-06-26 18:55] Running 'pacman-color -R gvfs'
[2012-06-26 18:56] Running 'pacman -Sy'
[2012-06-26 18:56] synchronizing package lists
[2012-06-26 18:58] Running 'pacman-color -Sy'
[2012-06-26 18:58] synchronizing package lists
[2012-06-26 19:01] Running 'pacman -Sy'
[2012-06-26 19:01] synchronizing package lists
[2012-06-26 19:03] Running 'pacman -Sy'
[2012-06-26 19:03] synchronizing package lists
[2012-06-26 19:12] Running 'pacman -Sy'
[2012-06-26 19:12] synchronizing package lists
[2012-06-26 19:16] Running 'pacman-color -Sy'
[2012-06-26 19:16] synchronizing package lists
[2012-06-26 19:33] Running 'pacman -Sy'
[2012-06-26 19:33] synchronizing package lists
[2012-06-26 20:29] Running 'pacman -Sy'
[2012-06-26 20:29] synchronizing package lists
[2012-06-26 22:29] Running 'pacman -Sy'
[2012-06-26 22:29] synchronizing package lists
[2012-06-26 23:39] Running 'pacman -Sy'
[2012-06-26 23:39] synchronizing package lists
[2012-06-27 08:46] Running 'pacman -Sy'
[2012-06-27 08:46] synchronizing package lists
[2012-06-27 08:52] Running 'pacman -Sy'
[2012-06-27 08:52] synchronizing package lists
[2012-06-27 08:54] Running 'pacman-color -Sy'
[2012-06-27 08:54] synchronizing package lists
[2012-06-27 08:55] starting full system upgrade
[2012-06-27 08:55] Running 'pacman-color -S -u'
[2012-06-27 08:55] starting full system upgrade
[2012-06-27 09:01] upgraded aurvote (1.2-1 -> 1.3-1)
[2012-06-27 09:01] upgraded hwids (20120512-1 -> 20120611-1)
[2012-06-27 09:01] upgraded systemd-tools (185-2 -> 185-3)
[2012-06-27 09:01] upgraded xz (5.0.3-2 -> 5.0.4-1)
[2012-06-27 09:01] upgraded libsystemd (185-2 -> 185-3)
[2012-06-27 09:01] upgraded dbus-core (1.4.20-2 -> 1.6.0-5)
[2012-06-27 09:01] upgraded bluez (4.100-1 -> 4.101-1)
[2012-06-27 09:01] upgraded burp (1.6.8-1 -> 1.6.9-1)
[2012-06-27 09:01] upgraded dbus-glib (0.98-1 -> 0.100-1)
[2012-06-27 09:01] upgraded chromium (19.0.1084.56-1 -> 20.0.1132.43-1)
[2012-06-27 09:01] upgraded clutter-gst (1.5.6-1 -> 1.6.0-1)
[2012-06-27 09:01] upgraded poppler (0.20.0-1 -> 0.20.1-1)
[2012-06-27 09:01] upgraded cups-filters (1.0.18-2 -> 1.0.18-3)
[2012-06-27 09:01] upgraded dbus (1.4.20-1 -> 1.6.0-1)
[2012-06-27 09:02] upgraded foomatic-db (1:4.0.15_20120406-1 -> 1:4.0.16_20120626-1)
[2012-06-27 09:02] upgraded foomatic-filters (1:4.0.15_20120406-1 -> 1:4.0.16_20120626-1)
[2012-06-27 09:02] upgraded foomatic-db-engine (1:4.0.15_20120406-1 -> 1:4.0.16_20120626-1)
[2012-06-27 09:02] upgraded git (1.7.11-1 -> 1.7.11.1-1)
[2012-06-27 09:02] upgraded grub2-common (1:2.00beta4-1 -> 1:2.00beta6-1)
[2012-06-27 09:02] upgraded grub2-bios (1:2.00beta4-1 -> 1:2.00beta6-1)
[2012-06-27 09:02] upgraded hplip (3.12.6-1 -> 3.12.6-2)
[2012-06-27 09:02] upgraded poppler-glib (0.20.0-1 -> 0.20.1-1)
[2012-06-27 09:02] upgraded inkscape (0.48.3.1-3 -> 0.48.3.1-4)
[2012-06-27 09:02] >> Traceroute is now provided by core/traceroute
[2012-06-27 09:02] upgraded iputils (20101006-2 -> 20101006-3)
[2012-06-27 09:02] upgraded libgadu (1.11.1-1 -> 1.11.2-1)
[2012-06-27 09:02] upgraded libreoffice-common (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-base (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-calc (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-draw (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-gnome (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-impress (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-kde4 (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-math (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-sdk (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-sdk-doc (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libreoffice-writer (3.5.4-1 -> 3.5.4-2)
[2012-06-27 09:02] upgraded libtiff (4.0.1-1 -> 4.0.2-1)
[2012-06-27 09:02] upgraded libusbx (1.0.11-2 -> 1.0.12-1)
[2012-06-27 09:02] upgraded libwbclient (3.6.5-3 -> 3.6.6-1)
[2012-06-27 09:02] upgraded linux-firmware (20120227-2 -> 20120625-1)
[2012-06-27 09:02] >>> Updating module dependencies. Please wait ...
[2012-06-27 09:02] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-06-27 09:02] ==> Building image from preset: 'default'
[2012-06-27 09:02] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-06-27 09:02] ==> Starting build: 3.4.4-2-ARCH
[2012-06-27 09:02] -> Running build hook: [base]
[2012-06-27 09:02] -> Running build hook: [udev]
[2012-06-27 09:02] -> Running build hook: [autodetect]
[2012-06-27 09:02] -> Running build hook: [pata]
[2012-06-27 09:02] -> Running build hook: [scsi]
[2012-06-27 09:02] -> Running build hook: [sata]
[2012-06-27 09:02] -> Running build hook: [filesystems]
[2012-06-27 09:02] -> Running build hook: [usbinput]
[2012-06-27 09:02] -> Running build hook: [fsck]
[2012-06-27 09:02] -> Running build hook: [v86d]
[2012-06-27 09:02] -> Running build hook: [plymouth]
[2012-06-27 09:02] -> Running build hook: [consolefont]
[2012-06-27 09:02] -> Running build hook: [keymap]
[2012-06-27 09:02] ==> Generating module dependencies
[2012-06-27 09:02] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-06-27 09:02] ==> Image generation successful
[2012-06-27 09:02] ==> Building image from preset: 'fallback'
[2012-06-27 09:02] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-06-27 09:02] ==> Starting build: 3.4.4-2-ARCH
[2012-06-27 09:02] -> Running build hook: [base]
[2012-06-27 09:02] -> Running build hook: [udev]
[2012-06-27 09:02] -> Running build hook: [pata]
[2012-06-27 09:02] -> Running build hook: [scsi]
[2012-06-27 09:02] -> Running build hook: [sata]
[2012-06-27 09:02] -> Running build hook: [filesystems]
[2012-06-27 09:02] -> Running build hook: [usbinput]
[2012-06-27 09:02] -> Running build hook: [fsck]
[2012-06-27 09:02] -> Running build hook: [v86d]
[2012-06-27 09:02] -> Running build hook: [plymouth]
[2012-06-27 09:02] -> Running build hook: [consolefont]
[2012-06-27 09:02] -> Running build hook: [keymap]
[2012-06-27 09:02] ==> Generating module dependencies
[2012-06-27 09:02] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-06-27 09:02] ==> Image generation successful
[2012-06-27 09:02] upgraded linux (3.4.3-1 -> 3.4.4-2)
[2012-06-27 09:02] upgraded lxdm (0.4.1-12 -> 0.4.1-13)
[2012-06-27 09:02] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2012-06-27 09:02] upgraded pacman-mirrorlist (20120211-1 -> 20120626-1)
[2012-06-27 09:02] upgraded qt (4.8.2-1 -> 4.8.2-2)
[2012-06-27 09:02] upgraded poppler-qt (0.20.0-1 -> 0.20.1-1)
[2012-06-27 09:02] upgraded python-dbus-common (1.1.0-2 -> 1.1.1-1)
[2012-06-27 09:02] upgraded python-dbus (1.1.0-2 -> 1.1.1-1)
[2012-06-27 09:02] upgraded python2-dbus (1.1.0-2 -> 1.1.1-1)
[2012-06-27 09:02] upgraded python3-xynexdg (2012.02.28.12269-1 -> 2012.6-1)
[2012-06-27 09:02] upgraded smbclient (3.6.5-3 -> 3.6.6-1)
[2012-06-27 09:02] >>> texlive: updating the filename database...
[2012-06-27 09:02] mktexlsr: Updating /etc/texmf/ls-R...
[2012-06-27 09:02] mktexlsr: Updating /usr/share/texmf/ls-R...
[2012-06-27 09:02] mktexlsr: Updating /var/lib/texmf/ls-R...
[2012-06-27 09:02] mktexlsr: Done.
[2012-06-27 09:02] recreating all formats... done.
[2012-06-27 09:02] (logs are under /var/lib/texmf/web2c/<engine>/<formatname>.log)
[2012-06-27 09:02] upgraded texlive-bin (2011.3-7 -> 2011.3-8)
[2012-06-27 09:03] upgraded wine (1.5.6-1 -> 1.5.7-1)
[2012-06-27 09:03] upgraded xinetd (2.3.15-1 -> 2.3.15-2)
[2012-06-27 09:03] upgraded xterm (279-1 -> 281-1)
[2012-06-27 09:04] Running 'pacman-color -U --noconfirm /tmp/yaourt-tmp-root/PKGDEST.0dR/google-chrome-20.0.1132.43-1-i686.pkg.tar.xz'
[2012-06-27 09:04] upgraded google-chrome (19.0.1084.56-1 -> 20.0.1132.43-1)
[2012-06-27 09:05] Running 'pacman-color -S --asdeps --needed extra/vala'
[2012-06-27 09:05] installed vala (0.16.1-1)
[2012-06-27 09:09] Running 'pacman-color -R synapse'
[2012-06-27 09:09] removed synapse (0.2.8.2-3)
[2012-06-27 09:09] Running 'pacman-color -R -'
[2012-06-27 09:09] removed vala (0.16.1-1)
[2012-06-27 09:09] removed libzeitgeist (0.3.12-1)
[2012-06-27 09:09] removed gtkhotkey (0.2.1-4)
[2012-06-27 09:11] Running 'pacman-color -S --asdeps --needed extra/bzr extra/vala extra/gnome-common extra/zeitgeist ayatana/libzeitgeist ayatana/gtkhotkey ayatana/zeitgeist-datahub'
[2012-06-27 09:12] installed bzr (2.5.1-1)
[2012-06-27 09:12] installed vala (0.16.1-1)
[2012-06-27 09:12] installed gnome-common (3.4.0.1-2)
[2012-06-27 09:12] installed xapian-core (1.2.10-1)
[2012-06-27 09:12] installed zeitgeist (0.9.0.1-1)
[2012-06-27 09:12] installed libzeitgeist (0.3.12-1)
[2012-06-27 09:12] installed gtkhotkey (0.2.1-2)
[2012-06-27 09:12] installed zeitgeist-datahub (0.7.0-2)
[2012-06-27 09:25] Running 'pacman -Sy'
[2012-06-27 09:25] synchronizing package lists
[2012-06-27 09:28] Running 'pacman -Sy'
[2012-06-27 09:28] synchronizing package lists
[2012-06-27 10:30] Running 'pacman -Sy'
[2012-06-27 10:30] synchronizing package lists
[2012-06-27 11:31] Running 'pacman -Sy'
[2012-06-27 11:31] synchronizing package lists
[2012-06-27 15:17] Running 'pacman -Sy'
[2012-06-27 15:17] synchronizing package listsI noticied that this error only occours when I am in the X session. So when I log in the tty, my partition is read-and-write, but when I make "startx" or "xinit" or when I log from the slim, the partition pecames read-only
And when I try to umount the partition, I receave a error that says the partition is already in use by some programs and cannot be umounted.
Here's the umount error:
[root@B1 ~]# umount /media/Lucas
umount: /media/Lucas: target is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))Then I execute 'lsof | grep /media/Lucas' to see what process arestill using the partition '/media/Lucas', although my user is loged off
[root@B1 ~]# lsof | grep /media/Lucas/
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/batata/.gvfs
Output information may be incomplete.
zeitgeist 3732 lucas mem-r REG 8,4 32768 641423 /media/Lucas/.local/share/zeitgeist/activity.sqlite-shm
zeitgeist 3732 lucas 8ur REG 8,4 1024 641321 /media/Lucas/.local/share/zeitgeist/activity.sqlite
zeitgeist 3732 lucas 9u REG 8,4 764024 641328 /media/Lucas/.local/share/zeitgeist/activity.sqlite-wal
zeitgeist 3732 lucas 10ur REG 8,4 32768 641423 /media/Lucas/.local/share/zeitgeist/activity.sqlite-shm
gdbus 3732 3733 lucas mem-r REG 8,4 32768 641423 /media/Lucas/.local/share/zeitgeist/activity.sqlite-shm
gdbus 3732 3733 lucas 8ur REG 8,4 1024 641321 /media/Lucas/.local/share/zeitgeist/activity.sqlite
gdbus 3732 3733 lucas 9u REG 8,4 764024 641328 /media/Lucas/.local/share/zeitgeist/activity.sqlite-wal
gdbus 3732 3733 lucas 10ur REG 8,4 32768 641423 /media/Lucas/.local/share/zeitgeist/activity.sqlite-shmThen I discovered that this problems occours with the probrams 'zeitgeist' and 'gdbus' (sometimes a process named 'gvfs' appear)
When I check the dmesg log, there's some entries about REISERFS (my partition is reiserfs)
[ 11.016046] REISERFS (device sda4): found reiserfs format "3.6" with standard journal
[ 11.016059] REISERFS (device sda4): using ordered data mode
[ 11.016061] reiserfs: using flush barriers
[ 11.027408] REISERFS (device sda4): journal params: device sda4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[ 11.027541] REISERFS (device sda4): checking transaction log (sda4)
[ 12.240056] REISERFS (device sda4): replayed 30 transactions in 1 seconds
[ 13.521794] REISERFS (device sda4): Using r5 hash to sort names
[ 13.521825] REISERFS (device sda4): Removing [651270 651271 0x0 SD]..done
[ 13.536961] REISERFS (device sda4): Removing [219665 650551 0x0 SD]..done
[ 13.536997] REISERFS (device sda4): Removing [219665 278120 0x0 SD]..done
[ 13.537009] REISERFS (device sda4): There were 3 uncompleted unlinks/truncates. Completed
[ 14.589013] r8169 0000:04:00.0: eth0: link down
[ 14.589064] r8169 0000:04:00.0: eth0: link down
[ 14.589077] NOHZ: local_softirq_pending 08
[ 14.589208] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 16.171787] r8169 0000:04:00.0: eth0: link up
[ 16.171943] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 26.656982] eth0: no IPv6 routers present
[ 45.254430] fuse init (API version 7.18)
[ 78.945782] EXT4-fs (sda2): re-mounted. Opts: commit=0
[ 90.043879] REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=25, free_space=65352 rdkey
[ 90.043882] REISERFS error (device sda4): vs-5150 search_by_key: invalid format found in block 112751990. Fsck?
[ 90.043884] REISERFS (device sda4): Remounting filesystem read-only
[ 90.043887] REISERFS error (device sda4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [645418 665333 0x0 SD]
[ 91.934728] REISERFS warning (device sda4): clm-6006 reiserfs_dirty_inode: writing inode 401095 on readonly FS
[ 193.265175] REISERFS (device sda4): found reiserfs format "3.6" with standard journal
[ 193.265223] REISERFS (device sda4): using ordered data mode
[ 193.265225] reiserfs: using flush barriers
[ 193.273074] REISERFS (device sda4): journal params: device sda4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[ 193.273265] REISERFS (device sda4): checking transaction log (sda4)
[ 193.944555] REISERFS (device sda4): replayed 13 transactions in 0 seconds
[ 195.113610] REISERFS (device sda4): Using r5 hash to sort names
[ 281.123718] REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=25, free_space=65352 rdkey
[ 281.123721] REISERFS error (device sda4): vs-5150 search_by_key: invalid format found in block 112751990. Fsck?
[ 281.123724] REISERFS (device sda4): Remounting filesystem read-only
[ 281.123727] REISERFS error (device sda4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [645418 665333 0x0 SD]
[ 282.264652] REISERFS warning (device sda4): clm-6006 reiserfs_dirty_inode: writing inode 243889 on readonly FS
[ 283.619855] REISERFS warning (device sda4): clm-6006 reiserfs_dirty_inode: writing inode 416365 on readonly FS
[ 3219.850110] REISERFS (device sda4): found reiserfs format "3.6" with standard journal
[ 3219.850136] REISERFS (device sda4): using ordered data mode
[ 3219.850139] reiserfs: using flush barriers
[ 3219.858009] REISERFS (device sda4): journal params: device sda4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[ 3219.858142] REISERFS (device sda4): checking transaction log (sda4)
[ 3219.894036] REISERFS (device sda4): replayed 9 transactions in 0 seconds
[ 3220.313195] REISERFS (device sda4): Using r5 hash to sort names
[ 3234.353534] REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=25, free_space=65352 rdkey
[ 3234.353538] REISERFS error (device sda4): vs-5150 search_by_key: invalid format found in block 112751990. Fsck?
[ 3234.353540] REISERFS (device sda4): Remounting filesystem read-only
[ 3234.353543] REISERFS error (device sda4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [645418 665333 0x0 SD]
[ 3235.231615] REISERFS warning (device sda4): clm-6006 reiserfs_dirty_inode: writing inode 243890 on readonly FSAnd when I boot my system, appears a entry named "NOHZ" during the running of rc scripts
[ 14.589077] NOHZ: local_softirq_pending 08If the problem continues, I will be forced to formate both my system partition (/) and my home partition (/media/Lucas) and reinstall ArchLinux
Thanks, and sorry for my bad english ;-P
Last edited by Seninha (2012-06-27 19:43:15)
Offline
#4 2012-06-27 20:01:41
- Terminator
- Member
- From: Belgium
- Registered: 2012-05-07
- Posts: 265
Re: Partition becames read-only when login to user
I think you just need to do a filecheck on sda4. Also, the pacman -Sy are still strange to me, do you use a helper (like yaourt)? If so, try updating normally (using pacman).
edit: Why don't you end the sda4 line in fstab on a 2, so that it gets checked automatically?
Last edited by Terminator (2012-06-27 20:03:28)
Offline
#5 2012-06-27 20:10:56
- fsckd
- Forum Fellow
- Registered: 2009-06-15
- Posts: 4,173
Re: Partition becames read-only when login to user
You shouldn't do pacman -Sy like that. My favorite post on why it's not a good idea: https://bbs.archlinux.org/viewtopic.php … 61#p802661. Not sure if it's contributed to your current problems but it will certainly be an issue in the future.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
#6 2012-06-27 20:12:16
- Seninha
- Member
- From: Brasília - Brasil
- Registered: 2012-04-05
- Posts: 14
Re: Partition becames read-only when login to user
yes, I use yaourt.
Offline
#7 2012-06-27 21:28:16
- Seninha
- Member
- From: Brasília - Brasil
- Registered: 2012-04-05
- Posts: 14
Re: Partition becames read-only when login to user
About the check file system, I runned the fsck.reiserfs and the partition is VERY damaged.
I runned this command:
fsck.reiserfs --fix-fixable /dev/sda4Sadly, I didn't save the output of this command (and I cannot run it again, once the fs is already fixed)
When the process of fsck finished, it said that I must execute it again with the option '--rebuild-tree',
that will check every block, node, inode, journaly nodes and other of this stuff, and will rebuild the
entire filesystem's tree...
It is executing here now, and is VERY slow, probably I have to leave my computer turned on during all the night...
Last edited by Seninha (2012-06-27 21:28:42)
Offline
#8 2012-06-29 14:46:01
- Seninha
- Member
- From: Brasília - Brasil
- Registered: 2012-04-05
- Posts: 14
Re: Partition becames read-only when login to user
I executed the fsck.reiserfs. And now I can run the X server without receiving errors.
This problem got solved, but another appeared
Well... In the partition /dev/sda4 I had only the Music, Images, Videos, Documents directories (and others directories generated by the "xdg-user-dir" command)
But after performing the filesystem checking, a entire linux hierarchy directory was built in the partition.
Now there is directories bin/, boot/, var/, and others togheter with my user directories.
Here's a image (my system is in Portuguese, not English):
So... is that normal, and can I remove these directories?
Last edited by Seninha (2012-06-29 14:56:29)
Offline
#9 2012-06-29 15:40:37
- DSpider
- Member
- From: Romania
- Registered: 2009-08-23
- Posts: 2,273
Re: Partition becames read-only when login to user
How exactly (and why) did you change the default user dir? Can you confirm that you actually changed it?
Run this and post the output:
$HOMEIf those folders are empty (check with 'sudo ls -l ~/boot') , you can safely delete them. My advice is to use the UUID in fstab for sda4 as well, not just for sda2 and 3. Maybe fsck.reiserfs got them mixed up somehow.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
#10 2012-06-29 15:47:31
- Seninha
- Member
- From: Brasília - Brasil
- Registered: 2012-04-05
- Posts: 14
Re: Partition becames read-only when login to user
How exactly (and why) did you change the default user dir? Can you confirm that you actually changed it?
Run this and post the output:
$HOMEIf those folders are empty (check with 'sudo ls -l ~/boot') , you can safely delete them. My advice is to use the UUID in fstab for sda4 as well, not just for sda2 and 3. Maybe fsck.reiserfs got them mixed up somehow.
I change the default user dir while creating the user with adduser program. Here's my user's line in /etc/passwd
lucas:x:1000:100:Lucas de Sena:/media/Lucas/:/bin/bashThe output of '$HOME':
$ $HOME
bash: /media/Lucas/: É um diretórioAnd these folders are not empty, see:
$ sudo ls -l ~/boot/
total 15
drwxr-xr-x 2 root root 448 Jan 18 17:55 grub
-rw-r--r-- 1 root root 10566609 Jan 18 17:53 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 2389730 Jan 18 17:53 initramfs-linux.img
-rw-r--r-- 1 root root 2955168 Jan 14 06:19 vmlinuz-linux
$ sudo ls -l ~/usr/
total 36
drwxr-xr-x 3 root root 12560 Jan 18 17:26 bin
drwxr-xr-x 66 root root 7080 Jan 18 17:26 include
drwxr-xr-x 34 root root 12864 Jan 18 17:26 lib
drwxr-xr-x 11 root root 264 Dez 19 2011 local
drwxr-xr-x 2 root root 3696 Jan 18 17:26 sbin
drwxr-xr-x 46 root root 1128 Jan 18 17:26 share
drwxr-xr-x 3 root root 88 Jan 18 17:25 srcLast edited by Seninha (2012-06-29 15:51:31)
Offline
#11 2012-06-29 16:04:48
- DSpider
- Member
- From: Romania
- Registered: 2009-08-23
- Posts: 2,273
Re: Partition becames read-only when login to user
Did you install or try to backup any Linux distributions lately?
You circled a "mount" folder. That's not a standard folder.
And nor is "bmp". Edit: Oh, it's "tmp"... Stupid font.
Last edited by DSpider (2012-06-29 16:17:57)
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
#12 2012-06-29 18:19:00
- Trent
- Member
- From: Baltimore, MD (US)
- Registered: 2009-04-16
- Posts: 990
Re: Partition becames read-only when login to user
Ok, here's what happened.
You, or the previous user of the hard drive (I'm guessing it was you), once had a Linux filesystem (or most of one) on part of it. We'll call this Partition Layout A. Then you decided to repartition the drive, resulting in Partition Layout B. (Actually you may have gone through several repartitionings between A and B, but let's keep it simple.)
Think about what's actually on the physical hard drive platter. Originally (when it came from the manufacturer), most of it was probably uninitialized or zero. But then you took a section of it (under Partition Layout A) and put ReiserFS on it. Now, that section of hard drive has some portions of it that aren't random -- they contain directories and files saved according to the ReiserFS scheme.
Then you repartitioned it with Partition Layout B. As it happens, under Partition Layout B, the section of disk used for /dev/sda4 overlaps some or all of the disk that contained a ReiserFS partition under Partition Layout A. So far, no problem; you create a new, empty, ReiserFS filesystem on the new /dev/sda4, and you put some new stuff on it. Some of the new stuff overwrites the old stuff; what's overwritten is gone forever. But some of the old stuff is still there, in limbo -- it exists on the disk, but it's not referred to by any directory, so there's no path to it and no way to access it through the file system. It has no purpose except to be overwritten with new data. (I could be getting some of this not exactly right; I'm not an expert on ReiserFS, just experienced with file system failures.)
So far, no problem, everything going according to plan. But you have another issue. Your hard drive is failing.[1] More specifically, a small portion of your hard drive that happens to right now be part of /dev/sda4, is bad in one way or another. This went unnoticed for a while, but somewhere along the line, something that X needs to read to start up got written to that portion of the disk. This caused an I/O call to fail. Badly. And ReiserFS noticed for the first time that something was seriously wrong on disk, and set itself read-only in order to prevent you from causing more damage by continuing to try to write to it. (I've had personal experience with this feature recently and it was quite confusing when I first encountered it.)
So suddenly your filesystem is readonly, and since you can't start your X session when your $HOME isn't writable, xinit fails. What's more, every time you try to start X, it tries to read (or write) that same file, and ReiserFS again tries to save you by marking itself readonly. But when you log in to the console, whatever-it-is in the bad portion of the disk isn't in use, and so you can continue to use text mode with $HOME read-write as if nothing's wrong.
So you go online and ask for help, and Terminator quite correctly advises you to check the filesystem, so you run fsck --fix-fixable on /dev/sda. But here's where the old Partition Layout A becomes a problem. You see, fsck can tell the disk is damaged, but it can't know which parts are okay and which ones aren't. So it looks at the data on the disk, and it sees alongside /Downloads, /Videos, /Desktop etc. a bunch of other stuff like /media, /mnt, /srv, /var ... all stuff that was part of your old Linux install back under Partition Layout A. It notices that these other directories aren't listed as members of / even though they're on the disk. But fsck can't tell whether that's because they really don't belong, or because the entries for them have been accidentally deleted. So it errs on the side of preserving data and adds entries for them in / in order to make the filesystem consistent; that's what --fix-fixable really does.
(Note on lost+found: this directory is created by fsck to store rescued files when it doesn't know where else to put them.)
Bam, suddenly your old Linux install is sharing the disk with your $HOME, like some kind of parasitic zombie. It's not even good for anything anymore because you've overwritten parts of it (that couldn't be retrieved by fsck), but you've still got those that could right there alongside the rest of your $HOME.
What should you take away from this? There's nothing wrong with the way you set your home directory (although I'd tend to mount stuff on /home/Lucas rather than changing your home directory to somewhere else); you didn't mess anything up by doing pacman -Sy (although you still shouldn't do that); and you won't ruin your system by removing the stuff that suddenly appeared in your $HOME -- those directories are just artifacts of an older Linux install. Furthermore, you should probably plan on replacing your hard drive pretty soon...
[1] A failing hard drive is not the only possible cause of the symptoms you've experienced, but unless you have evidence to indicate otherwise, you should assume this is the case, and take immediate steps to back up your data and look into buying a new drive.
Last edited by Trent (2012-06-29 18:22:18)
Offline
#13 2012-06-29 18:31:24
- Inxsible
- Forum Fellow
- From: Chicago
- Registered: 2008-06-09
- Posts: 9,183
Re: Partition becames read-only when login to user
tl;dr -- hard drive failing. Make backups.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
#14 2012-06-29 19:52:40
- Trent
- Member
- From: Baltimore, MD (US)
- Registered: 2009-04-16
- Posts: 990
Re: Partition becames read-only when login to user
tl;dr -- hard drive failing. Make backups.
Quite so.
Offline
#15 2012-06-29 22:57:11
- Seninha
- Member
- From: Brasília - Brasil
- Registered: 2012-04-05
- Posts: 14
Re: Partition becames read-only when login to user
Inxsible wrote:tl;dr -- hard drive failing. Make backups.
Quite so.
Hard drive failing. Make backups. By a new HD.
Well... I tried to delete these folders, but after deleting them, the partition becomes read-only again and the folders reappears after rebooting.
Thank you so much, Trent!!
Edit: that's what really happened. I had ArchLinux installed in this section of HD (in gparted, it seems to be at the end of HD). Then I repartitionned the Hard Drive.
I had ArchLinux installed in a very small partition at the end of HD, because my main OS was Ubuntu, and I installed ArchLinux there just for testing.
I liked Arch and removed the Ubuntu's partition at the beginning of the HD, and put ArchLinux there, and at the end of the disk, I created my user's partition (with personal data, like music and photos), that is the current /dev/sda4
Last edited by Seninha (2012-06-30 12:25:22)
Offline