Chris Mason oracle.com> writes:
>
> Excerpts from Vladi Gergov's message of 2010-10-29 16:53:42 -0400:
> > >>> gypsyops @ /mnt > sudo mount -o degraded /dev/sdc das3/
> > Password:
> > mount: wrong fs type, bad option, bad superblock on /dev/sdc,
> >missing codepage or helper program, o
Hello,
Somehow my subvolume with /home got corrupted. When I booted the machine this
morning (after perfectly normal shutdown) it gave me a bunch of kernel errors. I
found out that if I comment out my /home entry in fstab, it would boot ok. So
the / is not corrupted. I then booted from the live CD
On Sun, Oct 09, 2011 at 02:14:19PM -0500, Mitch Harder wrote:
> On Tue, Oct 4, 2011 at 10:54 AM, Josef Bacik wrote:
> > I noticed while running xfstests 83 that if we didn't have enough space to
> > delete our inode the orphan cleanup would just loop. This is because it
> > keeps
> > finding the
Hi,
I have high IO-Wait on the ods (ceph), the osd are running a v3.1-rc9
kernel.
I also experience high IO-rates, around 500IO/s reported via iostat.
Device: rrqm/s wrqm/s r/s w/srkB/swkB/s
avgrq-sz avgqu-sz await r_await w_await svctm %util
sda 0.0
On Tue, Oct 4, 2011 at 10:54 AM, Josef Bacik wrote:
> I noticed while running xfstests 83 that if we didn't have enough space to
> delete our inode the orphan cleanup would just loop. This is because it keeps
> finding the same orphan item and keeps trying to kill it but can't because we
> don't
I just realized that this is still the same warning I reported some month ago.
I thought that this had been fixed with
25d37af374263243214be9d912cbb46a8e469bc7
which is included in the kernel I'm using. So I think there must be
another Problem.
Regards,
Christian
2011/10/9 Christian Brunner :
I gave btrfs "for-chris" from josef's github repo a try in our ceph
cluster. During the rebuild I git the following warning.
Everything still seems to work... Should I be concerned?
Thanks,
Christian
[12554.886362] [ cut here ]
[12554.891693] WARNING: at fs/btrfs/inode.c:
