Date: Mon, 13 Apr 2015 17:06:10 +0200 From: "lokadamus@gmx.de" <lokadamus@gmx.de> To: matheyden@gmail.com, freebsd-questions@freebsd.org Subject: Re: System hangs on rm after upgrade to 10.1 with UFS Message-ID: <552BDB62.3030309@gmx.de> In-Reply-To: <552BCEEF.4096.A69CE8C@matheyden.gmail.com> References: <551BFF9C.22917.CCA7BA9B@matheyden.gmail.com>, <5522A200.9050206@gmx.de> <552BCEEF.4096.A69CE8C@matheyden.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/13/15 16:13, matheyden@gmail.com wrote: >> On 04/01/15 16:24, matheyden@gmail.com wrote: >>> Anyone have any idea what may be causing the problem? Is this a bug in >>> FreeBSD 10.1? >>> >>> Thanks. >>> >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >>> >> Can you give an answer about which file make this problem (dmesg or >> other logfile)? >> Is this a windows system? They have a little problem with a path over >> 255 signs (but this error begins with 240 signs or early). >> >> Or make you just a little first april joke? >> Greeting > > I'm not sure which file the process gets stuck on, is there an easy way to > find out? > > Nothing appears to be written to the log files when executing the command, > outside of the rsnapshot log: > http://pastebin.com/uVPfWYtT > > dmesg: > http://pastebin.com/t3HBYH73 > > My test host is running in VirtualBox on Windows 7, but the issue was > first found on a physical system running FreeBSD 10.1 backing up a host > running FreeBSD 10.0, so no windows involvement there. > > Thanks. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > Do you get a question about a shell? It looks it can't found it's root.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?552BDB62.3030309>