From: Josef Bacik <josef@redhat.com>
To: miyamoto moesasji <miyamoto.31b@gmail.com>
Cc: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: Unexpected ENOSPC on a SSD-drive after day of uptime, kernel?2.6.32-rc5
Date: Thu, 5 Nov 2009 20:25:15 -0500 [thread overview]
Message-ID: <20091106012514.GE22737@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <fe72f2c80911051507t7fbb95c0s2134bf2018a6a413@mail.gmail.com>
On Thu, Nov 05, 2009 at 11:07:27PM +0000, miyamoto moesasji wrote:
> I'm not 100% sure what is the correct answer.
>
> This is a clean install, just installed this weekend so the system
> itself has only been running with the 2.6.32-rc5 kernel, nothing older
> than that and the drive itself was completely new/clean. However for
> the install itself I've used SystemRescueCD which was using a 2.6.31.1
> kernel. Hence the partitions have been formatted using the kernel
> 2.6.31.1 and that is also the kernel used during the install of the
> system.
>
Yeah if most of the data was put on the disk under the old kernel then its
likely everything was skewed towards metadata and thats why you are having
problems. Theres not much more I can say other than sorry :(. If you can, try
copying the data from that volume to a new volume, format the old volume, and
copy it back under the new kernel and it should work out better. Thanks,
Josef
prev parent reply other threads:[~2009-11-06 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 20:38 Unexpected ENOSPC on a SSD-drive after day of uptime, kernel 2.6.32-rc5 miyamoto moesasji
2009-11-05 21:02 ` Josef Bacik
2009-11-05 20:55 ` miyamoto moesasji
2009-11-05 21:55 ` Unexpected ENOSPC on a SSD-drive after day of uptime, kernel?2.6.32-rc5 Josef Bacik
2009-11-05 22:37 ` miyamoto moesasji
2009-11-05 22:43 ` Josef Bacik
2009-11-05 23:07 ` miyamoto moesasji
2009-11-06 1:25 ` Josef Bacik [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=20091106012514.GE22737@dhcp231-156.rdu.redhat.com \
--to=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miyamoto.31b@gmail.com \
/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