[zfs] doesn't unmount at shutdown
I ve done the tutorial fr installing zfs on archlinux as a root system but i still have some problem.
I've used that one :
https://wiki.archlinux.org/index.php/In … nux_on_ZFS
When i boot my computer i have the emergency bash and i must import / export my pool.
I've already done :
systemctl enable zfs.service
here is my /usr/lib/systemd/system/zfs.service :
[Unit]
Description=Zettabyte File System (ZFS)
Documentation=man:zfs(8) man:zpool(8)
DefaultDependencies=no
After=cryptsetup.target
Before=local-fs.target
Conflicts=shutdown.target umount.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/modprobe zfs
#ExecStart=/usr/bin/zpool import -c /etc/zfs/zpool.cache -aN
#ExecStart=/usr/bin/zfs mount -a
#ExecStart=/usr/bin/zfs share -a
ExecStop=/usr/bin/swapoff -a
ExecStop=/usr/bin/zfs umount -a
ExecStop=/usr/bin/zpool export zroot
[Install]
WantedBy=local-fs.target
and here is a journalctl --unit=zfs
-- Logs begin at Sun 2013-09-15 08:49:49 CEST, end at Mon 2013-09-16 09:53:19 CEST. --
Sep 15 08:58:21 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
[1;39m-- Reboot --[0m
Sep 15 09:01:18 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
[1;39m-- Reboot --[0m
Sep 15 09:04:44 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
Sep 15 09:06:09 Kusanagi systemd[1]: Stopping Zettabyte File System (ZFS)...
[1;39m-- Reboot --[0m
Sep 15 09:08:28 Kusanagi systemd[1]: zfs.service: main process exited, code=exited, status=1/FAILURE
Sep 15 09:08:28 Kusanagi systemd[1]: Failed to start Zettabyte File System (ZFS).
Sep 15 09:08:28 Kusanagi systemd[1]: Unit zfs.service entered failed state.
[1;39m-- Reboot --[0m
Sep 15 09:33:54 Kusanagi zpool[416]: failed to open cache file: No such file or directory
Sep 15 09:33:54 Kusanagi systemd[1]: zfs.service: main process exited, code=exited, status=1/FAILURE
Sep 15 09:33:54 Kusanagi systemd[1]: Failed to start Zettabyte File System (ZFS).
Sep 15 09:33:54 Kusanagi systemd[1]: Unit zfs.service entered failed state.
[1;39m-- Reboot --[0m
Sep 15 10:15:54 Kusanagi systemd[1]: [/usr/lib/systemd/system/zfs.service:18] Missing '='.
Sep 15 10:18:34 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:32:12 Kusanagi systemd[1]: [/usr/lib/systemd/system/zfs.service:18] Missing '='.
Sep 15 10:32:18 Kusanagi systemd[1]: [/usr/lib/systemd/system/zfs.service:18] Missing '='.
Sep 15 10:37:06 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:48:19 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:49:12 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:49:33 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:49:54 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:50:22 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:51:16 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:51:44 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:51:53 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:53:38 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:53:44 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 10:56:40 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 11:00:45 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 11:05:38 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
Sep 15 11:12:32 Kusanagi systemd[1]: Cannot add dependency job for unit zfs.service, ignoring: Unit zfs.service failed to load: Bad message. See system logs and 'systemctl status zfs.service' for details.
[1;39m-- Reboot --[0m
Sep 15 22:05:17 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
[1;39m-- Reboot --[0m
Sep 16 05:55:32 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
[1;39m-- Reboot --[0m
Sep 16 07:33:39 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
and here is a systemctl status zfs.service :
systemctl status zfs.service
zfs.service - Zettabyte File System (ZFS)
Loaded: loaded (/usr/lib/systemd/system/zfs.service; enabled)
Active: active (exited) since Mon 2013-09-16 07:33:39 CEST; 2h 47min ago
Docs: man:zfs(8)
man:zpool(8)
Process: 405 ExecStart=/sbin/modprobe zfs (code=exited, status=0/SUCCESS)
Sep 16 07:33:39 Kusanagi systemd[1]: Started Zettabyte File System (ZFS).
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
and i've already done a # systemctl daemon-reload
Any idea ?
regards
Bussiere
seiichiro0185 wrote:
I had this problem too in the beginning, but did solve it by setting the hostid like this:
~# hostid > /etc/hostid
After this I rebuilt my initrd with
~# mkinitcpio -p linux
After these two steps I could remove the zfs_force from my kernel line and it works without a problem since then.
This solution f*******ed up my installation and now i'am have a real pain to reinstall my system because there is a version problem with the zfs module :
https://bbs.archlinux.org/viewtopic.php … 0#p1331360
And it may also have f***ed up my dd.
Bussiere
Similar Messages
-
Systemd and cifs unmount at shutdown problem
I have configured my cifs mounts in /etc/fstab, they have the noauto,x-systemd.automount option. (not the cause of the problem, but theoretically systemd should handle it better)
It all works ok, except at shutdown. Systemd brings the network down BEFORE unmounting the cifs mounts. This results in 1m30s of wait until the unmount fails due to timeout.
This has been happening a long time ago. When I'm in a hurry I just use sysrq to terminate all, but I would like to disable the sysrq key in my system.
Any clues?
* It happens with wicd and networkmanager
Last edited by eduardo.eae (2014-03-04 22:46:25)seiichiro0185 wrote:
I had this problem too in the beginning, but did solve it by setting the hostid like this:
~# hostid > /etc/hostid
After this I rebuilt my initrd with
~# mkinitcpio -p linux
After these two steps I could remove the zfs_force from my kernel line and it works without a problem since then.
This solution f*******ed up my installation and now i'am have a real pain to reinstall my system because there is a version problem with the zfs module :
https://bbs.archlinux.org/viewtopic.php … 0#p1331360
And it may also have f***ed up my dd.
Bussiere -
If I don't unmount a hard drive partition,etc. before shutting down the computer will it mess things up?
Hopefully not, but you always run the risk of corruption. Any time a disk is writing and it gets shut down unexpectedly you're going to have some data loss. With that being said, I've never known my base Linux system being hurt by unclean shutdowns.
-
Finder is not running. Relaunch doesn't work. Shutdown/restart doesn't work
Unable to get FInder running.
Applications trying to access files on the hardrive get stuck with the spinning wheel.
Finder relaunch doesn't do anything.
Shutdown/restart doesn't help.Hi:
PRAM:
http://docs.info.apple.com/article.html?path=Mac/10.6/en/26871.html
SMC:
http://support.apple.com/kb/HT3964
Barry -
Root filesystem not cleanly unmounted on shutdown
I have installed arch on a EEEPC701 on a flash card that is connected to the USB port. The filesystem is ext2. All is fine except that I often get error on the filesystem. Quite often the filesystem is marched clean but if I force a fsck on it I nevertheless get errors. I have modified /etc/rc.shutdown to do sync;sleep 5 just before the shutting down (after having remounted it ro) but the problem persists. Has anyone an idea; should it be possible to unmount it completely before the shutdown instead of remounting it ro? Might it be the problem?
Hi olive,
I don't know a lot about ext2 but if you do an fsync while disk filesystems are ro it won't have any effect I guess, so maybe you can put it earlier in the rc.shutdown script.
I found a thread on linux kernel mailing list related to your issue, not sure if it's still relevant though because it's about 2.4 kernels. anyway, here's the link:
http://lkml.indiana.edu/hypermail/linux … /1417.html
cheers, -
/home not unmounting during shutdown?
Hi,
If I shutdown the computer using "init 5/ init 6" or "shutdown -y -i5 / shutdown -y -i6" from my user account (after doing su ofcourse) I get the following error messages:
umount: /home/girish busy
umount: /home busy
cannot unmount: '/export/home': device busy
cannot unmount: '/export': device busy
/export/home is a local directory and appears to be mounted as a loopback FS (lofi).
But if I logout -> login as root -> init 5 then I don't get these error messages.
Why is /home not getting unmounted? or are these just harmless messages?Right. Because your account is still running, the umount cannot succeed at that point.
During shutdown the system will attempt to unmount filesystems. Some might not succeed due to running programs. That's generally okay though. At the end of the shutdown it will still cleanly unmount all local filesystems. For the most part, this is a harmless message.
Darren -
Hi,
Everytime Time Machine does a back up it seems to work fine, but the disk doesn't get ejected. Then they all start to accumulate in the finder window side bars. (They don't appear on the Desktop). See this for example:
http://www.dawg.ca/files/timemachine.png
Any ideas what's up?
Thanks.Hi, never saw anything like it! Drag all those backups off your sidebar and "Poof!" them.
Then go to Users/yourname/Library/Preferences and trash these two files:
com.apple.finder.plist
com.apple.sidebarlists.plist
Then, restart.
(You will have to reset a few finder prefs the way you like them.)
-mj -
HP550 halts and doesn't complete the shutdown
Hi All,
Having a problem with what I believe is acpi. If I press the power button on my laptop or use the shutdown option in xfce, the screen instantly goes dark but the power button continues to glow. I've added a few flags onto the kernel load line in the grub menu file which didn't seem to solve anything.
How can I proceed in getting a proper shutdown or where do I look to establish how to do it?
ThanksSee also: iTunes for Windows: Troubleshooting security software issues
and iOS 5: Updating your device to iOS 5 -
Hello,
I've had my new MacBook Pro for awhile now (I upgraded from my PB G4), and I have a consistant problem with my iPods not unmounting after they update. I have my iTunes set so that they automatically update when connected, and none of them are set into disk mode or anything like that. What happens is that, I would say 9 times out of 10, iTunes will display "iPod update is complete," but the blinking "no" symbol stays on my iPod, and it stays on my desktop. I can drag them to the trash and eject tehm, but that isn't what is supposed to happen! This happens if I have only one iPod connected, or all of them. Any help would be greatly apprectiated!
P.S. Permission have been repaired, cron scripts run, etc.
MacBook Pro Mac OS X (10.4.6) 2.16 GHz, 100GB, 1GB RAM,this is probably not going to be much consolation... but i'm experiencing exactly the same problem.
the difference for me is that i've had the ipod (80g) for 2 months now and until this week it worked fine.. no, it hasn't been dropped, or submerged in a pint of beer or anything like that.
i've tried numerous times to reset it and re-sync with itunes... but it seems to fail at random points throughout the process.. sometimes within the first 50 tracks, and then other times - the most gutting - around 90% done.
last night i did a surface scan of it.. no bad blocks found.. i formatted it with the zero blocks setting... and still it comes up with that error when syncing.
i'm basically running out of ideas... my next test will be to try it without the dock and using a different cable...
i purchased my ipod from an online retailer... as i say, it's been less than 3 months.. can i take it in to apple under warranty? what's the time limit? (it says 1 year for all apple hardware on the apple site - that must apply to ipods?)
powerbook g4 w/ ipod 80g Mac OS X (10.4.8) -
Mail with Yahoo account doesn't exit when shutdown or logout
Hi,
I'm using OS X Mail with a Yahoo Imap Account (setup by Mail itself) on a new MB Air.
Reading, writing Mail works fine, but: when logging out or restarting the system, the mail program (in background, hidden display) does not quit. After some seconds I get a message from the system saying that I have to quit Mail (translated from german) manually for the system to restart.
This behavior does not occur always, but sporadically (each 3rd or 5th time).
If I display the 'Activity' window of Mail in this cases, I can see that there are 2 jobs waiting forever: 'empty the trash' and 'logoff imap server' (translated again). One of them (or both?) seems to be a problem for the Mail application causing the endless waiting.
All other Mail acounts (iCloud, Google) do not have this problem, only Yahoo. The Problem can also be reproduced on two other Macs with fresh created Yahoo Email acounts.
Sorry for my bad english. I hope someone has a solution/hint for my problem.
Greets from Germany,
PeterTry re-indexing Spotlight..
Spotlight – Re-index -
Systemd doesn't umount (encrypted) /home and /tmp on shutdown
Hi all,
as this is my first post in this BBS, I hope I'm actually posting in the correct forum. I also did some research but couldn't really find answers.
I have a problem with systemd on shutdown. It doesn't unmount my encrypted home partition (and does not close the LUKS partition) and the /tmp partition. The corresponding output from journalctl would be this:
Oct 09 16:08:18 failenovo systemd[1]: Stopping Local File Systems.
Oct 09 16:08:18 failenovo systemd[1]: Stopped target Local File Systems.
Oct 09 16:08:18 failenovo systemd[1]: Unmounting /data...
Oct 09 16:08:18 failenovo systemd[1]: Unmounting /boot...
Oct 09 16:08:18 failenovo systemd[1]: Unmounting /home...
Oct 09 16:08:18 failenovo umount[3995]: umount: /home: target is busy.
Oct 09 16:08:18 failenovo umount[3995]: (In some cases useful info about processes that use
Oct 09 16:08:18 failenovo umount[3995]: the device is found by lsof(8) or fuser(1))
Oct 09 16:08:18 failenovo systemd[1]: Unmounting Temporary Directory...
Oct 09 16:08:18 failenovo systemd[1]: home.mount mount process exited, code=exited status=32
Oct 09 16:08:18 failenovo systemd[1]: Failed unmounting /home.
Oct 09 16:08:18 failenovo systemd[1]: Stopping File System Check on /dev/disk/by-uuid/a9395b0a-e3f8-41d7-9feb-d433173fd5ab...
Oct 09 16:08:18 failenovo systemd[1]: Stopped File System Check on /dev/disk/by-uuid/a9395b0a-e3f8-41d7-9feb-d433173fd5ab.
Oct 09 16:08:18 failenovo systemd[1]: Stopping /sys/devices/virtual/block/dm-1.
Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/sda1.
Oct 09 16:08:18 failenovo systemd[1]: Unmounted /boot.
Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-partuuid/28e18189-6b46-40b5-82f8-d550ee3df47a.
Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-partlabel/Linux\x20swap.
Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5000cca615e3f206-part1.
Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-id/ata-HITACHI_HTS543232A7A384_E2434243JK29XK-part1.
Oct 09 16:08:18 failenovo systemd[1]: Deactivated swap /dev/disk/by-uuid/4903864c-36f8-4f05-a722-ed726c9ae492.
Oct 09 16:08:18 failenovo umount[3997]: umount: /tmp: target is busy.
Oct 09 16:08:18 failenovo umount[3997]: (In some cases useful info about processes that use
Oct 09 16:08:18 failenovo umount[3997]: the device is found by lsof(8) or fuser(1))
Oct 09 16:08:18 failenovo systemd[1]: tmp.mount mount process exited, code=exited status=32
Oct 09 16:08:18 failenovo systemd[1]: Failed unmounting Temporary Directory.
Oct 09 16:08:18 failenovo systemd[1]: Unmounted /data.
Oct 09 16:08:18 failenovo systemd[1]: Stopping Local File Systems (Pre).
Oct 09 16:08:18 failenovo systemd[1]: Stopped target Local File Systems (Pre).
Oct 09 16:08:18 failenovo systemd[1]: Stopping Remount Root and Kernel File Systems...
Oct 09 16:08:18 failenovo systemd[1]: Stopped Remount Root and Kernel File Systems.
Oct 09 16:08:18 failenovo systemd[1]: Starting Shutdown.
Oct 09 16:08:18 failenovo systemd[1]: Reached target Shutdown.
Oct 09 16:08:23 failenovo systemd-cryptsetup[3989]: Failed to deactivate: Device or resource busy
Oct 09 16:08:23 failenovo systemd[1]: [email protected]: control process exited, code=exited status=1
Oct 09 16:08:23 failenovo systemd[1]: Stopped Cryptography Setup for home.
Oct 09 16:08:23 failenovo systemd[1]: Unit [email protected] entered failed state.
Oct 09 16:08:23 failenovo systemd[1]: Starting Unmount All Filesystems.
Oct 09 16:08:23 failenovo systemd[1]: Reached target Unmount All Filesystems.
Now, with the usual sysv-init this wouldn't be a problem but with systemd (which I'm new to) this poses a problem. I don't know where to start debugging this issue, really. I haven't found a way to run a script directly before and after the umount.target units starts so I can't really see which files are open or what the problem is at this point.
Is it possible to drop to a shell on such errors and inspect the problem manually? Or does anyone have a suggestion why systemd doesn't want to unmount these filesystems?
Here's my /etc/fstab:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/root LABEL=ROOT
UUID=27fed041-7765-4f63-a895-a7592113165b / ext4 rw,relatime,data=ordered,discard 0 1
# /dev/mapper/home LABEL=HOME
UUID=a9395b0a-e3f8-41d7-9feb-d433173fd5ab /home ext4 rw,relatime,data=ordered,discard 0 2
# /dev/sdb1
UUID=1573-8C74 /boot/ vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sda1 LABEL=SWAP
UUID=f5097167-6e12-4548-8bef-5f83942a1848 none swap defaults 0 0
# /dev/sda2 LABEL=DATA
UUID=dffd1518-d3b5-4d05-8b13-76e6fd841963 /data ext4 defaults 0 2
and my /etc/crypttab:
# <name> <device> <password> <options>
home UUID=01f3da5d-1ca0-4bf2-b5a1-cfe69c597707 /etc/keys/home.key luks,discard
If you need more information, please do tell! Thanks in advance.
Cheers,
gegenschallI think the /home part of the issue for me is at least partially due to how I have mpd configured. I start it with my X session and it persists after I log out, keeping a few files in my home folder open. If I make sure it is not running, log out to LightDM, and use its menu to reboot, I do not get a journal message about /home. If I kill mpd, but instead issue a `systemctl reboot/poweroff` command from a terminal in X, the problem returns. Is this normal? I guess I expected everything to be automatically cleaned up.
/tmp, on the other hand, remains a mystery. If I remove it from my /etc/fstab - to use the default tmp.mount (tmpfs) systemd provides - the problem goes away. But if I keep it as is, and do something silly like replace /bin/umount with this:
#!/bin/sh
/bin/test "$1" = "/tmp" && /bin/date -Ins >> /umount-tmp.log
/bin/test "$1" = "/tmp" && /bin/lsof /tmp >> /umount-tmp.log
/bin/umount.real "$@"
all I get is a list of times.
Also, I tried following the steps here (Shutdown Completes Eventually), but the output mostly mirrors what I get from journalctl:
[ 219.132058] systemd[1]: Stopping Local File Systems.
[ 219.132062] systemd[1]: local-fs.target changed active -> dead
[ 219.132066] systemd[1]: Job local-fs.target/stop finished, result=done
[ 219.132091] systemd[1]: Stopped target Local File Systems.
[ 219.132103] systemd[1]: Unmounting /home...
[ 219.132136] systemd[1]: About to execute: /bin/umount /home
[ 219.132329] systemd[1]: Forked /bin/umount as 908
[ 219.132402] systemd[1]: home.mount changed mounted -> unmounting
[ 219.132427] systemd[1]: Unmounting /storage...
[ 219.132480] systemd[1]: About to execute: /bin/umount /storage
[ 219.132735] systemd[1]: Forked /bin/umount as 909
[ 219.132805] systemd[1]: storage.mount changed mounted -> unmounting
[ 219.132825] systemd[1]: Unmounting /tmp...
[ 219.132872] systemd[1]: About to execute: /bin/umount /tmp
[ 219.133047] systemd[1]: Forked /bin/umount as 910
[ 219.133109] systemd[1]: tmp.mount changed mounted -> unmounting
[ 219.133136] systemd[1]: Unmounting /boot...
[ 219.133190] systemd[1]: About to execute: /bin/umount /boot
[ 219.133355] systemd[909]: Executing: /bin/umount /storage
[ 219.133388] systemd[1]: Forked /bin/umount as 911
[ 219.133452] systemd[1]: boot.mount changed mounted -> unmounting
[ 219.133676] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 219.134256] systemd[906]: Executing: /usr/lib/systemd/systemd-random-seed save
[ 219.134550] systemd[908]: Executing: /bin/umount /home
[ 219.135143] systemd[1]: Received SIGCHLD from PID 906 (systemd-random-).
[ 219.135170] systemd[1]: Got SIGCHLD for process 906 (systemd-random-)
[ 219.135222] systemd[1]: Child 906 died (code=exited, status=0/SUCCESS)
[ 219.135226] systemd[1]: Child 906 belongs to systemd-random-seed.service
[ 219.135235] systemd[1]: systemd-random-seed.service: control process exited, code=exited status=0
[ 219.135292] systemd[907]: Executing: /sbin/swapoff /dev/dm-2
[ 219.135462] systemd[910]: Executing: /bin/umount /tmp
[ 219.135487] systemd[1]: systemd-random-seed.service got final SIGCHLD for state stop
[ 219.135528] systemd[1]: systemd-random-seed.service changed stop -> dead
[ 219.135582] systemd[911]: Executing: /bin/umount /boot
[ 219.135622] systemd[1]: Job systemd-random-seed.service/stop finished, result=done
[ 219.135666] systemd[1]: Stopped Load/Save Random Seed.
[ 219.135695] systemd[1]: Unmounting /var...
[ 219.135730] systemd[1]: About to execute: /bin/umount /var
[ 219.135974] systemd[1]: Forked /bin/umount as 914
[ 219.136050] systemd[1]: var.mount changed mounted -> unmounting
[ 219.136290] systemd[1]: Accepted connection on private bus.
[ 219.136332] systemd[1]: Accepted connection on private bus.
[ 219.136529] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 219.136584] systemd[914]: Executing: /bin/umount /var
[ 219.136890] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 219.137193] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 219.137222] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 219.175076] systemd[1]: Received SIGCHLD from PID 754 (sudo).
[ 219.175102] systemd[1]: Got SIGCHLD for process 754 (sudo)
[ 219.175155] systemd[1]: Child 754 died (code=exited, status=129/n/a)
[ 219.200239] systemd[1]: Received SIGCHLD from PID 910 (umount).
[ 219.200267] systemd[1]: Got SIGCHLD for process 908 (umount)
[ 219.200338] systemd[1]: Child 908 died (code=exited, status=32/n/a)
[ 219.200342] systemd[1]: Child 908 belongs to home.mount
[ 219.200347] systemd[1]: home.mount mount process exited, code=exited status=32
[ 219.200357] systemd[1]: home.mount changed unmounting -> mounted
[ 219.200362] systemd[1]: Job home.mount/stop finished, result=failed
[ 219.200407] systemd[1]: Failed unmounting /home.
[ 219.200454] systemd[1]: Got SIGCHLD for process 910 (umount)
[ 219.200524] systemd[1]: Child 910 died (code=exited, status=32/n/a)
[ 219.200527] systemd[1]: Child 910 belongs to tmp.mount
[ 219.200532] systemd[1]: tmp.mount mount process exited, code=exited status=32
[ 219.200540] systemd[1]: tmp.mount changed unmounting -> mounted
[ 219.200544] systemd[1]: Job tmp.mount/stop finished, result=failed
[ 219.200571] systemd[1]: Failed unmounting /tmp.
[ 219.200607] systemd[1]: Got SIGCHLD for process 914 (umount)
[ 219.200666] systemd[1]: Child 914 died (code=exited, status=32/n/a)
[ 219.200669] systemd[1]: Child 914 belongs to var.mount
[ 219.200673] systemd[1]: var.mount mount process exited, code=exited status=32
[ 219.200681] systemd[1]: var.mount changed unmounting -> mounted
[ 219.200685] systemd[1]: Job var.mount/stop finished, result=failed
[ 219.200711] systemd[1]: Failed unmounting /var.
[ 219.200737] systemd[1]: Stopping File System Check on /dev/disk/by-uuid/98691163-fffa-4321-984c-3ba237083524...
[ 219.200763] systemd[1]: systemd-fsck@dev-disk-by\x2duuid-98691163\x2dfffa\x2d4321\x2d984c\x2d3ba237083524.service changed exited -> dead
[ 219.200769] systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-98691163\x2dfffa\x2d4321\x2d984c\x2d3ba237083524.service/stop finished, result=done
[ 219.200797] systemd[1]: Stopped File System Check on /dev/disk/by-uuid/98691163-fffa-4321-984c-3ba237083524.
[ 219.200816] systemd[1]: Redirecting stop request from dev-disk-by\x2duuid-98691163\x2dfffa\x2d4321\x2d984c\x2d3ba237083524.device to sys-devices-virtual-block-dm\x2d6.device.
[ 219.200823] systemd[1]: Stopping /sys/devices/virtual/block/dm-6.
[ 219.200876] systemd[1]: Accepted connection on private bus.
[ 219.201099] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 219.201186] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 219.201483] systemd[1]: Accepted connection on private bus.
[ 219.201642] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 219.201716] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 219.204043] systemd[1]: Accepted connection on private bus.
[ 219.204142] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 219.204219] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 219.234497] systemd[1]: dev-mapper-linux\x2dswap.swap changed active -> dead
[ 219.234606] systemd[1]: Job dev-mapper-linux\x2dswap.swap/stop finished, result=done
[ 219.234657] systemd[1]: Deactivated swap /dev/mapper/linux-swap.
[ 219.234674] systemd[1]: dev-linux-swap.swap changed active -> dead
[ 219.234751] systemd[1]: Job dev-linux-swap.swap/stop finished, result=done
[ 219.234805] systemd[1]: Deactivated swap /dev/linux/swap.
[ 219.234815] systemd[1]: dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2dDevEGGWf3oc8GE2g06c6XaLVUQEgo9cTTSwqNIhBSQfWKqAKYdL5kKqo0rCZ38xZ.swap changed active -> dead
[ 219.234970] systemd[1]: Job dev-disk-by\x2did-dm\x2duuid\x2dLVM\x2dDevEGGWf3oc8GE2g06c6XaLVUQEgo9cTTSwqNIhBSQfWKqAKYdL5kKqo0rCZ38xZ.swap/stop finished, result=done
[ 219.235007] systemd[1]: Deactivated swap /dev/disk/by-id/dm-uuid-LVM-DevEGGWf3oc8GE2g06c6XaLVUQEgo9cTTSwqNIhBSQfWKqAKYdL5kKqo0rCZ38xZ.
[ 219.235017] systemd[1]: dev-disk-by\x2did-dm\x2dname\x2dlinux\x2dswap.swap changed active -> dead
[ 219.235097] systemd[1]: Job dev-disk-by\x2did-dm\x2dname\x2dlinux\x2dswap.swap/stop finished, result=done
[ 219.235126] systemd[1]: Deactivated swap /dev/disk/by-id/dm-name-linux-swap.
[ 219.235135] systemd[1]: dev-disk-by\x2duuid-f8b1e59e\x2d9804\x2d44f0\x2daf79\x2d66810ee49206.swap changed active -> dead
[ 219.235214] systemd[1]: Job dev-disk-by\x2duuid-f8b1e59e\x2d9804\x2d44f0\x2daf79\x2d66810ee49206.swap/stop finished, result=done
[ 219.235244] systemd[1]: Deactivated swap /dev/disk/by-uuid/f8b1e59e-9804-44f0-af79-66810ee49206.
[ 219.235297] systemd[1]: Received SIGCHLD from PID 907 (swapoff).
[ 219.235323] systemd[1]: Got SIGCHLD for process 907 (swapoff)
[ 219.235390] systemd[1]: Child 907 died (code=exited, status=0/SUCCESS)
[ 219.235394] systemd[1]: Child 907 belongs to dev-dm\x2d2.swap
[ 219.235399] systemd[1]: dev-dm\x2d2.swap swap process exited, code=exited status=0
[ 219.235410] systemd[1]: dev-dm\x2d2.swap changed deactivating -> dead
[ 219.235956] systemd[1]: Job dev-dm\x2d2.swap/stop finished, result=done
[ 219.236044] systemd[1]: Deactivated swap /dev/dm-2.
[ 219.236131] systemd[1]: Got SIGCHLD for process 911 (umount)
[ 219.236192] systemd[1]: Child 911 died (code=exited, status=0/SUCCESS)
[ 219.236196] systemd[1]: Child 911 belongs to boot.mount
[ 219.236201] systemd[1]: boot.mount mount process exited, code=exited status=0
[ 219.236210] systemd[1]: boot.mount changed unmounting -> dead
[ 219.236294] systemd[1]: Job boot.mount/stop finished, result=done
[ 219.236322] systemd[1]: Unmounted /boot.
[ 219.236360] systemd[1]: Received SIGCHLD from PID 911 (n/a).
[ 219.236413] systemd[1]: Accepted connection on private bus.
[ 219.236551] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 219.237196] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 219.237321] systemd[1]: Accepted connection on private bus.
[ 219.237463] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 219.237814] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 219.238324] systemd[1]: Received SIGCHLD from PID 909 (umount).
[ 219.238348] systemd[1]: Got SIGCHLD for process 909 (umount)
[ 219.238404] systemd[1]: Child 909 died (code=exited, status=0/SUCCESS)
[ 219.238407] systemd[1]: Child 909 belongs to storage.mount
[ 219.238412] systemd[1]: storage.mount mount process exited, code=exited status=0
[ 219.238420] systemd[1]: storage.mount changed unmounting -> dead
[ 219.238509] systemd[1]: Job storage.mount/stop finished, result=done
[ 219.238540] systemd[1]: Unmounted /storage.
[ 219.238556] systemd[1]: Stopping Local File Systems (Pre).
[ 219.238562] systemd[1]: local-fs-pre.target changed active -> dead
[ 219.238566] systemd[1]: Job local-fs-pre.target/stop finished, result=done
[ 219.238592] systemd[1]: Stopped target Local File Systems (Pre).
[ 219.238604] systemd[1]: Stopping Remount Root and Kernel File Systems...
[ 219.238627] systemd[1]: systemd-remount-fs.service changed exited -> dead
[ 219.238631] systemd[1]: Job systemd-remount-fs.service/stop finished, result=done
[ 219.238656] systemd[1]: Stopped Remount Root and Kernel File Systems.
[ 219.238673] systemd[1]: Starting Shutdown.
[ 219.238676] systemd[1]: shutdown.target changed dead -> active
[ 219.238679] systemd[1]: Job shutdown.target/start finished, result=done
[ 219.238703] systemd[1]: Reached target Shutdown.
[ 219.239263] systemd[1]: Accepted connection on private bus.
[ 219.239382] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 219.239752] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 219.630816] systemd[1]: Received SIGCHLD from PID 486 (at-spi-bus-laun).
[ 219.630840] systemd[1]: Got SIGCHLD for process 486 (at-spi-bus-laun)
[ 219.630896] systemd[1]: Child 486 died (code=exited, status=0/SUCCESS)
[ 219.668697] systemd[1]: Received SIGCHLD from PID 449 (X).
[ 219.668725] systemd[1]: Got SIGCHLD for process 449 (X)
[ 219.668781] systemd[1]: Child 449 died (code=exited, status=0/SUCCESS)
[ 219.669379] systemd[1]: Accepted connection on private bus.
[ 219.669545] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 219.669606] systemd[1]: lightdm.service: cgroup is empty
[ 219.669636] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 220.420041] systemd[1]: Received SIGCHLD from PID 845 (sleep).
[ 220.420064] systemd[1]: Got SIGCHLD for process 845 (sleep)
[ 220.420103] systemd[1]: Child 845 died (code=exited, status=0/SUCCESS)
[ 221.914117] systemd[1]: Received SIGCHLD from PID 545 (dbus-launch).
[ 221.914141] systemd[1]: Got SIGCHLD for process 545 (dbus-launch)
[ 221.914184] systemd[1]: Child 545 died (code=exited, status=0/SUCCESS)
[ 221.914458] systemd[1]: Received SIGCHLD from PID 483 (dbus-launch).
[ 221.914486] systemd[1]: Got SIGCHLD for process 483 (dbus-launch)
[ 221.914529] systemd[1]: Child 483 died (code=exited, status=0/SUCCESS)
[ 221.915102] systemd[1]: Accepted connection on private bus.
[ 221.915222] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 221.915328] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 223.957616] systemd[1]: Received SIGCHLD from PID 904 (systemd-cryptse).
[ 223.957639] systemd[1]: Got SIGCHLD for process 904 (systemd-cryptse)
[ 223.957707] systemd[1]: Child 904 died (code=exited, status=1/FAILURE)
[ 223.957712] systemd[1]: Child 904 belongs to systemd-cryptsetup@crypt\x2dhome.service
[ 223.957720] systemd[1]: systemd-cryptsetup@crypt\x2dhome.service: control process exited, code=exited status=1
[ 223.957782] systemd[1]: systemd-cryptsetup@crypt\x2dhome.service got final SIGCHLD for state stop
[ 223.957818] systemd[1]: systemd-cryptsetup@crypt\x2dhome.service changed stop -> failed
[ 223.957904] systemd[1]: Job systemd-cryptsetup@crypt\x2dhome.service/stop finished, result=done
[ 223.957917] systemd[1]: Stopped Cryptography Setup for crypt-home.
[ 223.957928] systemd[1]: Unit systemd-cryptsetup@crypt\x2dhome.service entered failed state.
[ 223.958243] systemd[1]: Accepted connection on private bus.
[ 223.958397] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 223.958509] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 224.016365] systemd[1]: Received SIGCHLD from PID 905 (systemd-cryptse).
[ 224.016390] systemd[1]: Got SIGCHLD for process 905 (systemd-cryptse)
[ 224.016447] systemd[1]: Child 905 died (code=exited, status=1/FAILURE)
[ 224.016451] systemd[1]: Child 905 belongs to systemd-cryptsetup@crypt\x2dlinux.service
[ 224.016457] systemd[1]: systemd-cryptsetup@crypt\x2dlinux.service: control process exited, code=exited status=1
[ 224.016529] systemd[1]: systemd-cryptsetup@crypt\x2dlinux.service got final SIGCHLD for state stop
[ 224.016565] systemd[1]: systemd-cryptsetup@crypt\x2dlinux.service changed stop -> failed
[ 224.016661] systemd[1]: Job systemd-cryptsetup@crypt\x2dlinux.service/stop finished, result=done
[ 224.016676] systemd[1]: Stopped Cryptography Setup for crypt-linux.
[ 224.016687] systemd[1]: Unit systemd-cryptsetup@crypt\x2dlinux.service entered failed state.
[ 224.016703] systemd[1]: Starting Unmount All Filesystems.
[ 224.016707] systemd[1]: umount.target changed dead -> active
[ 224.016711] systemd[1]: Job umount.target/start finished, result=done
[ 224.016717] systemd[1]: Reached target Unmount All Filesystems.
[ 224.016728] systemd[1]: Starting Final Step.
[ 224.016731] systemd[1]: final.target changed dead -> active
[ 224.016734] systemd[1]: Job final.target/start finished, result=done
[ 224.016742] systemd[1]: Reached target Final Step.
[ 224.016754] systemd[1]: Starting Reboot...
[ 224.016866] systemd[1]: About to execute: /usr/bin/systemctl --force reboot
[ 224.017057] systemd[1]: Forked /usr/bin/systemctl as 928
[ 224.017193] systemd[1]: systemd-reboot.service changed dead -> start
[ 224.018230] systemd[928]: Executing: /usr/bin/systemctl --force reboot
[ 224.018328] systemd[1]: Accepted connection on private bus.
[ 224.018435] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
[ 224.018504] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
[ 224.019495] systemd[1]: Accepted connection on private bus.
[ 224.019712] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.Reboot() on /org/freedesktop/systemd1
[ 224.019734] systemd[1]: Shutting down.
[ 224.023022] systemd[1]: Hardware watchdog 'NV_TCO', version 0
[ 224.023031] systemd[1]: Failed to set timeout to 600s: Invalid argument
[ 224.023033] nv_tco: Unexpected close, not stopping watchdog!
[ 225.162099] systemd-journald[215]: Received SIGTERM
[ 225.515048] EXT4-fs (dm-6): re-mounted. Opts: (null)
[ 225.687382] EXT4-fs (dm-4): re-mounted. Opts: (null)
[ 225.796081] EXT4-fs (dm-3): re-mounted. Opts: (null)
[ 225.915129] EXT4-fs (dm-1): re-mounted. Opts: (null)
[ 225.919881] EXT4-fs (dm-1): re-mounted. Opts: (null)
[ 225.919911] EXT4-fs (dm-1): re-mounted. Opts: (null)
[ 226.283469] EXT4-fs (dm-1): re-mounted. Opts: data=ordered -
Leopard doesn't shutdown sometimes....
Sometimes happend that my MacBook doesn't want to shutdown. Normally I close MacBook to put it in stop mode without problem, but when I try to shutdown or restart Mac Os closes all icons and menù bar correctly: the dock remains open and nothing more happend. Some minutes later Mac Os tell me FINDER couldn't be closed.
Any solutions?OK....
but when happend how can I shutdown the system? I can do it by the power button only (pushing it for some seconds). I tried to use the command SHUTDOWN on the terminal but the system say I'm not a superuser. -
Hello,
I installed Solaris 10 x86 10/09 using ZFS in vSphere, and the disk image was expanded from 15G to 18G.
But Solaris still sees 15G.
How can I convince it to make notice of the expanded disk image, how can I grow the rpool?
Searched a lot, but all documents give answers about adding a disk, but not if the space is additionally allocated on the same disk.
-- Nicknikitelli wrote:
if that is really true what you are saying, then this is really disappointing!
Solaris can so many tricks, and in this specific case it drops behind linux, aix and even windows?
Not even growfs can help?Growfs will expand a UFS filesystem so that it can address additional space in its container (slice, metadevice, volume, etc.). ZFS doesn't need that particular tool, it can expand itself based on the autogrow property.
The problem is that the OS does not make the LUN expansion visible so that other things (like the filesystems) can use that space. Years and years ago, "disks" were static things that you didn't expect to change size. That assumption is hard coded into the Solaris disk label mechanics. I would guess that redoing things to remove that assumption isn't the easiest task.
If you have an EFI label, it's easier (still not great), but fewer steps. But you can't boot from an EFI disk, so you have to solve the problem with a VTOC/SMI label if you want it to work for boot disks.
Darren -
Cannot unmount mp3 player using thunar
Hi,
When I try to unmount my mp3 player using thunar, it doesn't unmount it (No problems with normal usb memories). When I fuser on it, after I tried unmount it, there seems to be like 10 processes using it. When I force quit them with
fuser -m /dev/sdc --kill
I return to terminal (jumping from X) and see a page full of errors. I can return to X with ctrl+alt+f7. My mp3 player is this: "Philips GoGear SA2RGA02SN RaGa 2GB"
I am using xfce4, with all group + xfce4-utils installed. I don't use login manager, my xinitrc and .bash_profile is as follows:
.bash_profile wrote:
[[ -f ~/.bashrc ]] && . ~/.bashrc
startx
.xinitrc wrote:if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec ck-launch-session dbus-launch xfce4-session
So, I was wondering what is the problem, and is there a way to make is work normally.
Last edited by yasar11732 (2011-07-07 21:11:53)I realized that fuser -m /dev/sdc gives all processes owned by me at that moment. For example, it give me a list of processes that corresponds to this:
yasar 1602 0.0 0.1 5392 1584 tty1 S+ Jul07 0:00 -bash
yasar 1607 0.0 0.1 5340 1416 tty1 S+ Jul07 0:00 /bin/sh /usr/bin/startx
yasar 1624 0.0 0.0 3180 664 tty1 S+ Jul07 0:00 xinit /home/yasar/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth.Z5Sbdk4zkQ
yasar 1631 0.0 0.0 2308 576 tty1 S Jul07 0:00 ck-launch-session dbus-launch xfce4-session
yasar 1638 0.0 0.0 3348 488 tty1 S Jul07 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
yasar 1639 0.0 0.0 2568 324 ? Ss Jul07 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
yasar 1648 0.0 0.6 29736 7736 tty1 Sl Jul07 0:00 xfce4-session
yasar 1652 0.0 0.1 3948 1804 ? Ss Jul07 0:02 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
yasar 1654 0.0 0.1 5688 2292 ? S Jul07 0:00 /usr/lib/xfce4/xfconf/xfconfd
yasar 1658 0.0 0.2 18872 3296 tty1 S Jul07 0:00 xfsettingsd
yasar 1659 0.0 0.7 22760 10088 tty1 S Jul07 0:00 xfwm4 --display :0.0 --sm-client-id 213d50e43-4189-4bd5-9bdd-88ba018ba437
yasar 1661 0.0 1.1 96096 14508 tty1 Sl Jul07 0:01 xfce4-panel --display :0.0 --sm-client-id 2a62dfc23-f36b-4649-ad64-20a924b5116d
yasar 1662 0.0 1.1 97084 14700 tty1 S Jul07 0:02 xfdesktop --display :0.0 --sm-client-id 26125b852-39ab-4370-a5b0-c7d1202d3eda
yasar 1663 0.0 2.8 164908 35964 tty1 S Jul07 0:03 pidgin --session 2c569a522-b558-498c-bf66-1f315a40afa9 --display :0.0
yasar 1666 0.0 0.6 90492 8204 ? Ssl Jul07 0:00 xfce4-power-manager --restart --sm-client-id 2f89cd8c8-0544-4d3a-a10b-dad5242710ee
yasar 1671 0.0 0.1 8000 2208 ? S Jul07 0:00 /usr/lib/gvfs/gvfsd
yasar 1672 0.0 0.2 20864 3696 tty1 S Jul07 0:00 xfce4-settings-helper --display :0.0 --sm-client-id 25a995b8d-9702-41bf-a2ae-f342bdc1ee79
yasar 1677 0.0 0.1 31104 2100 ? Ssl Jul07 0:00 /usr/lib/gvfs//gvfs-fuse-daemon /home/yasar/.gvfs
yasar 1682 0.0 0.5 19748 6932 tty1 S Jul07 0:00 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libsystray.so 1 14680110 systray Sistem çekmecesi Bildirim simgelerinin göründüğü alan
yasar 1684 0.0 0.3 34284 3924 ? S Jul07 0:00 /usr/lib/gvfs/gvfs-gdu-volume-monitor
yasar 1686 0.0 0.7 81500 9440 tty1 S Jul07 0:00 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libxfsm-logout-plugin.so 15 14680111 xfsm-logout-plugin Oturum Menüsü İçinde ekranı kilitle, askıya al, kapat veya çıkış yap seçenekleri yer alan bir menü gösterir
yasar 1710 0.0 0.6 19956 8100 tty1 S Jul07 0:00 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel-plugins/libdatetime.so 4 14680118 datetime Tarih & Saat Basit bir takvimi olan, tarih ve saat programcığı.
yasar 1711 0.0 0.9 104064 12216 tty1 Sl Jul07 0:00 /usr/lib/xfce4/panel-plugins/xfce4-mixer-plugin 7 14680119 xfce4-mixer-plugin Ses Düzenleyicisi Ses kartınız için ses düzeyi ayarı
yasar 1722 0.0 0.7 83736 9188 tty1 S Jul07 0:00 /usr/lib/xfce4/panel-plugins/xfce4-screenshooter-plugin 19 14680120 screenshooter Ekran görüntüsü Tüm ekranın, etkin pencerenin veya belirli bir alanın ekran görüntüsünü alır
yasar 1733 0.0 0.2 8608 3168 ? S Jul07 0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.11 /org/gtk/gvfs/exec_spaw/0
yasar 1744 0.0 1.0 93936 13108 tty1 Sl Jul07 0:00 xfce4-notes
yasar 1744 0.0 1.0 93936 13108 tty1 Sl Jul07 0:00 xfce4-notes
yasar 1746 0.0 0.7 83124 9996 tty1 S Jul07 0:00 xfce4-clipman
yasar 1749 0.0 2.8 243924 37020 tty1 Sl Jul07 0:08 /opt/dropbox/dropbox
yasar 1880 0.0 0.9 84240 11844 ? Ss Jul07 0:00 /usr/bin/xfrun4 --daemon
yasar 1927 0.0 1.4 115684 17920 ? Sl Jul07 0:03 /usr/bin/Thunar --daemon
yasar 1934 0.0 0.2 8516 3020 ? S Jul07 0:00 /usr/lib/gvfs/gvfsd-network --spawner :1.11 /org/gtk/gvfs/exec_spaw/1
yasar 1936 0.0 0.2 8312 2564 ? S Jul07 0:00 /usr/lib/gvfs/gvfsd-dnssd --spawner :1.11 /org/gtk/gvfs/exec_spaw/2
yasar 2024 4.5 19.5 311156 250340 tty1 Sl Jul07 20:32 /home/yasar/.local/lib/opera/opera
yasar 2040 0.0 0.9 85560 12296 ? S Jul07 0:00 leafpad /home/yasar/.bash_profile
yasar 2045 0.0 0.9 93572 11700 ? Ss Jul07 0:00 gvim /home/yasar/.xinitrc
yasar 2052 0.0 2.1 101436 27788 tty1 Sl 00:04 0:12 /home/yasar/.local/lib/opera//operapluginwrapper 59 63 /usr/lib/mozilla/plugins/libflashplayer.so
yasar 2053 0.0 0.0 3108 556 tty1 S 00:04 0:00 /home/yasar/.local/lib/opera//operaplugincleaner 2024
yasar 2314 0.1 0.8 82336 10324 ? S 07:25 0:00 /usr/lib/xfce4/notifyd/xfce4-notifyd
yasar 2319 0.0 0.9 55268 12388 ? Sl 07:25 0:00 /usr/lib/tumbler-1/tumblerd
yasar 2328 0.8 1.2 97348 15368 ? Ssl 07:26 0:00 terminal
And also, I can unmount it from terminal (it seems to be normally unmounted) but when I unplug it, it send me terminal (tty1), and in a couple of secons I can switch back to tty7 again. -
Problems with mount and unmount of network shares
Hi,
I use an Apple script to mount four network shares during startup of an OS 10.4.4 Powerbook. Unfortunately it seems that Tiger can't always mount them all. Sometimes it only mounts three of them, but pressing Command + K indicates that the fourth is already mounted because it's grayed out. How come I can't see it on neither the desktop nor the favorites list in a Finder window then?
I have a Tiger installation at home with Ciscos VPN Client 4.8 installed. I use that VPN client to gain access to the company's network. When the connection is established, I mount a share (with AFP over TCP/IP) on the company's server running Win2003 and ExtremeZ-IP.
When I close down Ciscos VPN Client, the mounted network share doesn't unmount automatically, and if I forget to toss that network drive in the trash before closing down or restarting my Mac, it hangs. Why can't it just unmount that drive automatically when the VPN connection is gone?
Regards
Thomas G. Madsen
Powermac G5 (2 x 1.8 Ghz) Mac OS X (10.4.4)This may happens because broadcasts do not go through an IPSec tunnel.
Browsing Network Neighborhood is a function of the Microsoft browsing service. Any problems are usually because the PC or master browsers do not function properly. Network Neighborhood is officially not supported. However, it works if configured correctly. Browsing Network Neighborhood works by obtaining the browse list from either a master or backup browser. This list is obtained locally on your LAN by using NetBIOS Broadcasts to locate domain browsers.
Inorder to resove this :
Make sure you have NetBIOS over TCP enabled on the adapter that you use to connect to the domain.
Refer this related links:
http://www.cisco.com/en/US/products/sw/secursw/ps2308/products_tech_note09186a0080194b4a.shtml
Maybe you are looking for
-
I owned an Apple Tv and since I upgrade my internet to higher speed my Apple Tv does not work. Please someone help.
-
Liquify Bug, PS CS6, Half-Baked Results (Repeatable)
Liquify mixes results from two different steps, and outputs them in a single file. Here are two examples. Steps to repeat: Open file in liquify. Perform liquification. (Extreme changes will slow the computer down and make it easier to repeat these
-
While troubleshooting another problem I discovered this error. Any thoughts on this? Thank you Fault bucket 90349650291, type 5 Event Name: SQLException64 Response: Not available Cab Id: 0 Problem signature: P1: ReportingServicesService.exe P2: 2011.
-
Updated to 8.0.2 and now POP3 connections delete emails
I updated a secondary Groupwise domain on our OES server to 8.0.2 to match the 8.0.2 running on our primary, Netware server. Users with smartphones were horrified to see emails disappearing from their Mailbox in front of their eyes. The emails gradua
-
Sybase datetime col...how to generate as timestamp col in oracle ddl
i'm having trouble understanding the date mapping... i'm taking the defaults (per http://dermotoneill.blogspot.com/2008/06/offline-data-move-dates.html)... but my sybase datetime columns are being generated as date columns in the oracle ddl. (so i lo