Re: No space left on device, problem

2013-10-27 Thread Chris Murphy
On Oct 27, 2013, at 4:46 PM, Chris Murphy wrote: > > On Oct 27, 2013, at 3:53 PM, Igor M 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.c

Error from Trying to Mount Btrfs

2013-10-27 Thread gatlin sullivan
I have the attached error from trying to mount btrfs on external hard drive. The F.S. was my primary system, then I dd'd it to an external and reinstalled Fedora. I tried to follow https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#Filesystem_can.27t_be_mounted_by_label. I used "# btrfs devi

Re: No space left on device, problem

2013-10-27 Thread Chris Murphy
On Oct 27, 2013, at 3:53 PM, Igor M 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 from this list: s

Re: No space left on device, problem

2013-10-27 Thread Igor M
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 'Retry

Re: Total fs size does not match with the actual size of the setup

2013-10-27 Thread Lester B
sudo btrfs fi df Data: total=5.62GB, used=4.96GB System: total=32.00MB, used=4.00KB Metadata: total=512.00MB, used=288.70MB -- 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 http://vger.kernel.or

Re: Total fs size does not match with the actual size of the setup

2013-10-27 Thread Brendan Hide
On 2013/10/27 10:27 PM, Lester B wrote: 2013/10/28 Hugo Mills : On Mon, Oct 28, 2013 at 04:09:18AM +0800, Lester B wrote: The btrfs setup only have one device of size 7 GiB but when I run df, the total size shown is 15 GiB. Running btrfs --repair I'd recommend not running btrfs check --rep

Re: Non-intelligent behaviour on device delete with multiple devices?

2013-10-27 Thread Brendan Hide
On 2013/10/27 07:33 PM, Hans-Kristian Bakke wrote: Hi Today I tried removing two devices from a multidevice btrfs RAID10 volume using the following command: --- btrfs device delete /dev/sdl /dev/sdk /btrfs --- It first removed device sdl and then sdk. What I did not expect however was that btrf

Re: 3.11 and 3.12rc continual hard lock ups

2013-10-27 Thread Sean Clarke
OK, hard another crash this afternoon - I had "dmesg -n7" set and this time (unusually) I had something in the logs: Oct 27 14:48:15 enterprise kernel: [23752.263442] INFO: task nfsd:1537 blocked for more than 120 seconds. Oct 27 14:48:15 enterprise kernel: [23752.263452] Not tainted 3.12.0-

Re: Total fs size does not match with the actual size of the setup

2013-10-27 Thread Lester B
2013/10/28 Hugo Mills : > On Mon, Oct 28, 2013 at 04:09:18AM +0800, Lester B wrote: >> The btrfs setup only have one device of size 7 GiB but >> when I run df, the total size shown is 15 GiB. Running >> btrfs --repair > >I'd recommend not running btrfs check --repair unless you really > know wh

Re: Total fs size does not match with the actual size of the setup

2013-10-27 Thread Hugo Mills
On Mon, Oct 28, 2013 at 04:09:18AM +0800, Lester B wrote: > The btrfs setup only have one device of size 7 GiB but > when I run df, the total size shown is 15 GiB. Running > btrfs --repair I'd recommend not running btrfs check --repair unless you really know what you're doing, or you've checked

Total fs size does not match with the actual size of the setup

2013-10-27 Thread Lester B
The btrfs setup only have one device of size 7 GiB but when I run df, the total size shown is 15 GiB. Running btrfs --repair displays an error "cache and super generation don't match, space cache will be invalidated." How can I correct the total fs size as shown in df? -- To unsubscribe from this

Re: btrfs unable to mount

2013-10-27 Thread luvar
Ehm, after one, or two days (computer was shut down normally to night), now I am not able to mount that btrfs partition. Nor btrfs-zero-log helps. I am going to reformat it, but uploading btrfs-image for further analyse if anybody wants. PS: I have used for this btrfs partition a bcache partitio

Non-intelligent behaviour on device delete with multiple devices?

2013-10-27 Thread Hans-Kristian Bakke
Hi Today I tried removing two devices from a multidevice btrfs RAID10 volume using the following command: --- btrfs device delete /dev/sdl /dev/sdk /btrfs --- It first removed device sdl and then sdk. What I did not expect however was that btrfs didn't remove sdk from the available drives when re

Re: No space left on device, problem

2013-10-27 Thread Igor M
On Sun, Oct 27, 2013 at 9:56 AM, Brendan Hide wrote: > On 2013/10/27 10:50 AM, Igor M wrote: >> >> On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski >> wrote: Still no messages. Parameter seems to be active as /sys/module/printk/parameters/ignore_loglevel is Y, but there are no >

Re: 3.11 and 3.12rc continual hard lock ups

2013-10-27 Thread Sean Clarke
Hi Chris, I set dmesg -n7 and didn't see anything extra logged (I had to use sudo to enable it. I am not familiar with sysrq-w and sysrq-t, however you ask "while it is locked", this is a "real" hard lock. everything is unresponsive and the machine even fails to respond to ping request. It happe

Re: No space left on device, problem

2013-10-27 Thread Brendan Hide
On 2013/10/27 10:50 AM, Igor M wrote: On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski 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

Re: No space left on device, problem

2013-10-27 Thread Igor M
On Sun, Oct 27, 2013 at 2:00 AM, Tomasz Chmielewski 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 kernel ?