From: Brian Chadwick <brianchad@westnet.com.au>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: cp hangs with large source tree
Date: Wed, 25 Jun 2014 15:37:09 +1000 [thread overview]
Message-ID: <53AA6005.2030405@westnet.com.au> (raw)
Hi,
Kernel 3.15.0 ... I tried copying a large tree full of many small files
(kernel source) onto a drive formatted with F2FS. The copy seems to
proceed normally, but when all files appear to be copied, cp seems to
hang and does not seem to terminate properly. Its waiting for something
I assume. This also happens with 3.16.0-rc{1,2}. cp responds to Ctrl-C
and terminates, and the files appear to be there on the F2FS partition.
It works as expected with Kernel 3.14.8
Any clues?
Brian
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
next reply other threads:[~2014-06-25 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 5:37 Brian Chadwick [this message]
2014-06-25 7:43 ` cp hangs with large source tree Jaegeuk Kim
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=53AA6005.2030405@westnet.com.au \
--to=brianchad@westnet.com.au \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.