From: Andi Kleen <ak@suse.de>
To: ext2-devel@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org
Subject: interesting way to break ext3 using loop devices
Date: Wed, 15 Nov 2006 15:36:20 +0100 [thread overview]
Message-ID: <200611151536.21066.ak@suse.de> (raw)
By mistake i found a sick way to break ext3:
Create a sparse (only consisting of a large hole) loop file on a ext3 file system.
losetup a loop device over it
Create a ext3 file system in the loop device
Mount it.
Copy the "parent" file system into the mounted loop fs with cp -rv
Eventually it will work on the copy of the loop file.
When you Ctrl-C it the system becomes quite confused:
- Syslog is flooded with IO errors
- The loop fs cannot be unmounted anymore
- sync gets stuck
Of course this was clearly an operator error and
copying a file system into itself is clearly a sick thing
to do, but still it shouldn't cause symptoms like this. Perhaps
it points to a deeper issue.
-Andi
next reply other threads:[~2006-11-15 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 14:36 Andi Kleen [this message]
2006-11-15 15:40 ` interesting way to break ext3 using loop devices Theodore Tso
2006-11-15 16:22 ` Bill Rugolsky Jr.
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=200611151536.21066.ak@suse.de \
--to=ak@suse.de \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@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.