From: Stephan Kulow <coolo@suse.de>
To: Doug Hunley <doug@hunley.homeip.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ok to stop e4defrag?
Date: Tue, 4 Aug 2009 11:41:47 +0200 [thread overview]
Message-ID: <200908041141.47771.coolo@suse.de> (raw)
In-Reply-To: <7284e2210908031239q1177490bk41bb0bca63af30da@mail.gmail.com>
Montag 03 August 2009 sent Doug Hunley:
> I started e4defrag against /dev/md3 on Jul 31 in a screen session, and
> it's still running. I've got a few things coming up shortly that are
> gonna require me to reboot this machine, but I'm not sure if its 'ok'
> to CTRL-C the e4defrag window or not. Advice? Also, how can I tell
> what it's currently working on? I passed the '-v' switch but I've not
> seen any progress indicators in the screen session.
It works fine here and it even outputs progress when not started with -v :)
I _think_ it's still reading the informations of your file system in when
it's not showing any progress.
And yes, there is little chance that you will break something in Ctrl-C
as all dangerous operations are atomic to user space. But don't sue me if I'm
wrong :)
Greetings, Stephan
prev parent reply other threads:[~2009-08-04 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 19:39 ok to stop e4defrag? Doug Hunley
2009-08-04 9:41 ` Stephan Kulow [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908041141.47771.coolo@suse.de \
--to=coolo@suse.de \
--cc=doug@hunley.homeip.net \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.