public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: linux-btrfs@vger.kernel.org
Subject: btrfs filesystem freeze
Date: Sun, 21 Dec 2008 00:26:21 +0100	[thread overview]
Message-ID: <550569572@web.de> (raw)

Hello,=20

i was testing btrfs a little bit for stability and i think i have found=
 an issue.

during some heavy activity (multiple processes writing/reading to compr=
essed /btrfs at the same time), i did some snapshots in a loop (every 1=
0 seconds).

very soon, all filesystem activity stopped, i.e. i cannot read/write an=
yting from/to /btrfs anymore.
this happens with latest git-unstable with kernel 2.6.27
nothing in dmesg.=20

besides that, the system seems ok.

as the system is a vmware virtual machine, i did a snapshot of the syst=
em state, so we can always go back to this state.

if somebody want`s to analyse this, please tell me what to do.

regards
roland

ps:
btw,  is there some bugzilla/bugtracker for btrfs ?
____________________________________________________________________
Psssst! Schon vom neuen WEB.DE MultiMessenger geh=F6rt?=20
Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3D3123

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2008-12-20 23:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-20 23:26 devzero [this message]
2008-12-21 11:13 ` btrfs filesystem freeze Yan Zheng
  -- strict thread matches above, loose matches on Subject: below --
2008-12-21 14:09 devzero
2008-12-22  0:55 ` Yan Zheng
2009-01-05 15:44   ` Chris Mason
2009-01-05 21:14     ` Yan Zheng
2009-01-05 21:24       ` Chris Mason
2008-12-23  0:26 devzero

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=550569572@web.de \
    --to=devzero@web.de \
    --cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox