From: Sergei Trofimovich <slyfox@gentoo.org>
To: Arne Jansen <sensille@gmx.net>
Cc: Chris Mason <chris.mason@oracle.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Li Zefan <lizf@cn.fujitsu.com>, Miao Xie <miaox@cn.fujitsu.com>
Subject: Re: Integration branch pushed out to btrfs-unstable
Date: Wed, 25 May 2011 23:41:10 +0300 [thread overview]
Message-ID: <20110525234110.669f4d71@sf> (raw)
In-Reply-To: <20110525214418.225ec273@sf>
[-- Attachment #1: Type: text/plain, Size: 2593 bytes --]
> > The commit
> >
> > commit c4f675cd40d955d539180506c09515c90169b15b
> > Author: Sergei Trofimovich <slyfox@gentoo.org>
> > Date: Fri May 20 20:20:30 2011 +0000
> >
> > btrfs: don't spin in shrink_delalloc if there is nothing to free
> >
> > gives me very early ENOSPC in my tests on a small volume (7GB).
>
> What king of test is that? I'd like to reproduce it.
> Does it do a lot of parallel I/O?
>
> May I ask you to try to reproduce the problem with this sole patch
> on top of linus master?
With Arne's params to fs_mark it triggers for 2.6.39+this patch.
I took 2GB loop device and the script [1].
$ ./make_it.sh
...
# /home/slyfox/dev/fs_mark/fs_mark -D 512 -t 16 -n 4096 -s 51200 -L7 -S0 -d /mnt/ut
# Version 3.3, 16 thread(s) starting at Wed May 25 23:35:06 2011
# Sync method: NO SYNC: Test does not issue sync() or fsync() calls.
# Directories: Time based hash between directories across 512 subdirectories with 180 seconds per subdirectory.
# File names: 40 bytes long, (16 initial bytes of time stamp with 24 random bytes at end of name)
# Files info: size 51200 bytes, written with an IO size of 16384 bytes per write
# App overhead is time in microseconds spent in the test not doing file writing related system calls.
FSUse% Count Size Files/sec App Overhead
fs_mark: write_file write failed: -1 No space left on device
fs_mark: write_file write failed: -1 No space left on device
fs_mark: write_file write failed: -1 No space left on device
...^C
$ .../btrfs fi df /mnt/ut/
Data: total=622.25MB, used=434.61MB
System: total=4.00MB, used=4.00KB
Metadata: total=417.50MB, used=6.69MB
$ sudo .../btrfs fi show /dev/loop0
Label: none uuid: ccb18c12-4cbe-458c-835a-30e767939121
Total devices 1 FS bytes used 441.31MB
devid 1 size 2.00GB used 1.02GB path /dev/loop0
[1] 'make_it.sh' script exposing bug:
export LANG=C
FS_MARK=$HOME/dev/fs_mark/fs_mark
MKFS_BTRFS=$HOME/dev/git/btrfs-progs-unstable/mkfs.btrfs
sz=2
the_file=${sz}G.img
mount_point=/mnt/ut
dd if=/dev/zero of="${the_file}" bs=1 count=1 seek=$((${sz}*1024*1024*1024-1))
$MKFS_BTRFS -d raid0 -m raid0 "${the_file}"
sudo mount -oloop "${the_file}" "${mount_point}"
sudo chown slyfox:users "${mount_point}"
chmod u+w "${mount_point}"
cd /tmp
$FS_MARK \
-D 512 -t 16 -n 4096 -s 51200 -L7 -S0 \
-d "${mount_point}"
sudo umount "${mount_point}"
--
Sergei
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-05-25 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 19:54 Integration branch pushed out to btrfs-unstable Chris Mason
2011-05-24 9:01 ` Arne Jansen
2011-05-24 9:50 ` Li Zefan
2011-05-25 12:35 ` Arne Jansen
2011-05-25 18:44 ` Sergei Trofimovich
2011-05-25 20:41 ` Sergei Trofimovich [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=20110525234110.669f4d71@sf \
--to=slyfox@gentoo.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=miaox@cn.fujitsu.com \
--cc=sensille@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).