On Mon, Oct 28, 2013 at 12:27 AM, Chris Murphy li...@colorremedies.com wrote:
On Oct 27, 2013, at 4:46 PM, Chris Murphy li...@colorremedies.com wrote:
On Oct 27, 2013, at 3:53 PM, Igor M igor...@gmail.com wrote:
I made some more tests. Disk is 3TB, first cca 225GB is copied without
On Oct 28, 2013, at 1:40 AM, Igor M igor...@gmail.com wrote:
dmesg: http://pastebin.com/t2H1QYye
You've got a warning related to pcie bridge on boot, with a trace that follows.
I don't know if this could be related to some problems.
[0.325976] [ cut here ]
[
On Sun, Oct 27, 2013 at 09:50:37AM +0100, Igor M wrote:
On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski t...@virtall.com wrote:
Still no messages. Parameter seems to be active as
/sys/module/printk/parameters/ignore_loglevel is Y, but there are no
messages in log files or dmesg. Maybe I
On Mon, Oct 28, 2013 at 6:57 PM, Chris Murphy li...@colorremedies.com wrote:
On Oct 28, 2013, at 1:40 AM, Igor M igor...@gmail.com wrote:
dmesg: http://pastebin.com/t2H1QYye
You've got a warning related to pcie bridge on boot, with a trace that
follows. I don't know if this could be
On Mon, Oct 28, 2013 at 8:05 PM, Josef Bacik jba...@fusionio.com wrote:
On Sun, Oct 27, 2013 at 09:50:37AM +0100, Igor M wrote:
On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski t...@virtall.com wrote:
Still no messages. Parameter seems to be active as
On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski t...@virtall.com wrote:
Still no messages. Parameter seems to be active as
/sys/module/printk/parameters/ignore_loglevel is Y, but there are no
messages in log files or dmesg. Maybe I need to turn on some kernel
debugging option and recompile
On 2013/10/27 10:50 AM, Igor M wrote:
On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski t...@virtall.com wrote:
Still no messages. Parameter seems to be active as
/sys/module/printk/parameters/ignore_loglevel is Y, but there are no
messages in log files or dmesg. Maybe I need to turn on some
On Sun, Oct 27, 2013 at 9:56 AM, Brendan Hide bren...@swiftspirit.co.za wrote:
On 2013/10/27 10:50 AM, Igor M wrote:
On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski t...@virtall.com
wrote:
Still no messages. Parameter seems to be active as
/sys/module/printk/parameters/ignore_loglevel
I made some more tests. Disk is 3TB, first cca 225GB is copied without errors.
Then errors 'No space left on device' begins.
Now if I use rsync with '--bwlimit' option no error occurs or if I
choose 'Retry' in Midnight Commander then continues
and after a while another error occurs and again
On Oct 27, 2013, at 3:53 PM, Igor M igor...@gmail.com wrote:
I made some more tests. Disk is 3TB, first cca 225GB is copied without errors.
Then errors 'No space left on device' begins.
Post the full entire dmesg somewhere please. pastebin.com is one option.
Chris Murphy--
To unsubscribe
On Oct 27, 2013, at 4:46 PM, Chris Murphy li...@colorremedies.com wrote:
On Oct 27, 2013, at 3:53 PM, Igor M igor...@gmail.com wrote:
I made some more tests. Disk is 3TB, first cca 225GB is copied without
errors.
Then errors 'No space left on device' begins.
Post the full entire
Hello,
I just upgraded kernel to 3.11.6 added new disk and created btrfs:
# mkfs.btrfs /dev/sdb
# mount -t btrfs -o compress=lzo,compress-force=lzo /dev/sdb
/usr/local/mysql/data
I started copying files from old disk and then I got 'No space left on
device', but there is a lot of space.
# df
Some more info, exact error message is:
cp: writing ‘/usr/local/mysql/data/gbdata/parts_0015.MYI’: No space
left on device
cp: failed to extend ‘/usr/local/mysql/data/gbdata/parts_0015.MYI’: No
space left on device
Files are 2.7G - 7.7G big.
On Sat, Oct 26, 2013 at 9:46 PM, Igor M
On Oct 26, 2013, at 1:46 PM, Igor M igor...@gmail.com wrote:
# mount -t btrfs -o compress=lzo,compress-force=lzo /
Why do you have two compression mount options? You need to pick one of these.
What to do ?
Are there any kernel messages reported by dmesg at the time the copy starts and
On Sat, Oct 26, 2013 at 11:35 PM, Chris Murphy li...@colorremedies.com wrote:
On Oct 26, 2013, at 1:46 PM, Igor M igor...@gmail.com wrote:
# mount -t btrfs -o compress=lzo,compress-force=lzo /
Why do you have two compression mount options? You need to pick one of these.
I removed one. I
On Oct 26, 2013, at 3:53 PM, Igor M igor...@gmail.com wrote:
I even added enospc_debug mount option, still no messages.
If it were kernel enospc, you should have messages in dmesg.
What version of btrfs progs when making the btrfs volume?
cp: failed to extend
On Sun, Oct 27, 2013 at 12:17 AM, Chris Murphy li...@colorremedies.com wrote:
On Oct 26, 2013, at 3:53 PM, Igor M igor...@gmail.com wrote:
I even added enospc_debug mount option, still no messages.
If it were kernel enospc, you should have messages in dmesg.
What version of btrfs progs
On Sun, Oct 27, 2013 at 12:22 AM, Igor M igor...@gmail.com wrote:
On Sun, Oct 27, 2013 at 12:17 AM, Chris Murphy li...@colorremedies.com
wrote:
On Oct 26, 2013, at 3:53 PM, Igor M igor...@gmail.com wrote:
I even added enospc_debug mount option, still no messages.
If it were kernel
Didn't see before. btrfs progs were compiled today form git.
# btrfs version
Btrfs v0.20-rc1-358-g194aa4a
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Still no messages. Parameter seems to be active as
/sys/module/printk/parameters/ignore_loglevel is Y, but there are no
messages in log files or dmesg. Maybe I need to turn on some kernel
debugging option and recompile kernel ?
Also I should mention that cca 230G+ data was copied before this
20 matches
Mail list logo
