From: "Michael B. Trausch" <mike@trausch.us>
To: linux-ext4@vger.kernel.org
Subject: "tune2fs -I 256" runtime---can it be interrupted safely?
Date: Sat, 1 Nov 2008 15:10:02 -0400 [thread overview]
Message-ID: <20081101151002.4ed9be99@zest> (raw)
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Hello,
I have a drive (a 250 GB external USB hard drive) which I wanted to
convert to 256 byte inodes and start using as an ext4 drive (currently
I use it as ext3). However, I started the tune2fs operation on 01 Nov
2008 02:27:34 -0400, and it is currently nearly 13 hours later, and the
operation is _still_ going at 100% of one core and operating on the
drive.
Three questions:
* Is this normal?
* How long can I expect this process to continue?
* Can it be (safely) interrupted if it will continue for a long time?
I converted my home directory to ext4 without issue and so I (stupidly,
I admit) did not take a backup of this 250 GB drive's contents before I
started the conversion process. Oops. Lesson learned. My thinking at
this point is that it would take _far_ less time to interrupt, backup,
and just use mkfs.ext4 on the drive and then restore (about 2 hours
instead of an unknown quantity which is already nearing 13 hours).
Thanks,
Mike Trausch
--
My sigfile ran away and is on hiatus.
http://www.trausch.us/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-11-01 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 19:10 Michael B. Trausch [this message]
2008-11-01 23:46 ` "tune2fs -I 256" runtime---can it be interrupted safely? Michael B. Trausch
2008-11-07 21:16 ` Andreas Dilger
2008-11-11 16:09 ` Michael B. Trausch
2008-11-14 8:30 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2008-11-14 12:49 Andreas Schultz
2008-11-14 21:06 ` Andreas Dilger
2008-11-15 5:50 ` Theodore Tso
2008-11-16 12:11 ` Andreas Schultz
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=20081101151002.4ed9be99@zest \
--to=mike@trausch.us \
--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.