From: Richard Weinberger <richard@nod.at>
To: <dedekind1@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: UBIFS: unlink failure
Date: Tue, 12 Jun 2012 23:56:35 +0200 [thread overview]
Message-ID: <332997dc8907401d45f417c18fd2aace@radon2.swed.at> (raw)
Hi!
While testing UBI fastmap I encountered a problem.
After multiple writes unlink fails.
This is my test case:
---cut---
function do_mount_write1()
{
ubiattach -m 0 /dev/ubi_ctrl
mount /dev/ubi0_0 /mnt/ -t ubifs
dd if=/dev/urandom of=/mnt/x bs=1M count=1
dd if=/dev/urandom of=/mnt/x bs=1M count=2
dd if=/dev/urandom of=/mnt/x bs=1M count=10
dd if=/dev/urandom of=/mnt/x bs=1M count=30
rm x
umount /mnt
ubidetach -m 0 /dev/ubi_ctrl
}
flash_eraseall /dev/mtd0
ubiattach -m 0 /dev/ubi_ctrl
ubimkvol -N test -s 100MiB /dev/ubi0
mkfs.ubifs /dev/ubi0_0
ubidetach -m 0 /dev/ubi_ctrl
do_mount_write1
---cut---
rm does newfstatat() and unlinkat(), both fail with ENOENT.
The issue is 100% reproducible on a current kernel (3.4)
Adding a "sleep 10" before the rm does _not_ help.
Thanks,
//richard
next reply other threads:[~2012-06-12 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 21:56 Richard Weinberger [this message]
2012-06-26 14:26 ` UBIFS: unlink failure Artem Bityutskiy
2012-06-26 14:28 ` Richard Weinberger
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=332997dc8907401d45f417c18fd2aace@radon2.swed.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox