I mounted the drive on my Debian stable system and deleted the '/tmp'
directory.
The boot sequence and time is back to normal now, thanks very much for the
help!
--
Regards
Marc
The command ls -l /tmp also blocks ...
The line before the lines shown in the file extract has an odd looking
path //tmp, do you think this may be problem ?
The st_size=117604352 looks very large, is this normal, does it
represent free disk space?
18:58:28 stat(//tmp,
On Wed, 22 Oct 2014 18:23:54 +1100 Marc Bonnor ma...@iprimus.com.au wrote:
The command ls -l /tmp also blocks ...
That pretty much confirms that it is a filesystem problem not directly
related to systemd.
The line before the lines shown in the file extract has an odd looking
path //tmp, do
I have run the strace command as suggested and attached the output.
I added the -t option to add a time stamp, the 4 minute delay shows up
very clearly.
The iotop man page describes the accumulate option;
-a, --accumulated
Show accumulated I/O instead of bandwidth. In this mode, iotop
shows
Marc Bonnor wrote:
I have run the strace command as suggested and attached the output.
18:58:28 open(/tmp,
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_NOFOLLOW|O_NOATIME|O_CLOEXEC) = 4
18:58:28 fstat(4, {st_mode=S_IFDIR|S_ISVTX|0777, st_size=117604352, ...}) = 0
18:58:28 fcntl(4, F_GETFL)
Marc Bonnor wrote:
I have also poked around in the debug shell during boot and there is almost no
cpu activity and the systemd-tmpfiles command has statuts 'D' uniteruptable
sleep.
I used iotop to view io activity during the boot and this 'Executing: /bin
/systemd-tmpfiles --create --remove
6 matches
Mail list logo
