Hey all, I run into no space left on device on a virtualbox After installing Debian 6 on a virtual machine I tried installing the KDE desktop The system HDD is 8Gb Both root (/) and /home are btrfs over LVM. While installing the packages I run into: no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0 bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total df shows only 74% used space on / kernel used: stock debian 6 2.6.32-5-686 At the moment I cannot access it with normal boot, only recovery mode. I can provide whatever info you would like as long as you think of a way to load the normal system and not the recovery mode. -- Caution: breathing may be hazardous to your health. -- 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
Hi Leonidas, Please check this: btrfs fi df /home If this shows much of your space used by metadata then please use: btrfs fi balance /home Note that this can take a long (>1 day) time to complete on a big FS. - Erik On 02/07/2011 10:21 PM, Leonidas Spyropoulos wrote:> Hey all, > > I run into no space left on device on a virtualbox > > After installing Debian 6 on a virtual machine > I tried installing the KDE desktop > > The system HDD is 8Gb > Both root (/) and /home are btrfs > over LVM. > > While installing the packages I run into: > > no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0 > bytes_reserved, > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total > > df shows only 74% used space on / > > kernel used: stock debian 6 2.6.32-5-686 > > At the moment I cannot access it with normal boot, only recovery mode. > > I can provide whatever info you would like as long as you think of a > way to load the normal system and not the recovery mode. > > > >-- 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
Hi, I had a similar problem on my Debian (squeeze) about a half year ago. I''ve described that on this mailing list. That was a main reason to migrate from brtfs (-o ssd) to ext4. I know it''s a pain for my SSD but I want to revert this fail system when it will be more stable. Thanks God it was added to Debian 6 and Ubuntu 10.10. Now there will be even more alpha/beta testers. And some problems will be noticed more frequently. When will you change status from experimental to stable in the kernel? Regards Robert. Dnia 2011-02-07, o godz. 22:27:14 Erik Logtenberg <erik@logtenberg.eu> napisał(a):> Hi Leonidas, > > Please check this: > > btrfs fi df /home > > If this shows much of your space used by metadata then please use: > > btrfs fi balance /home > > Note that this can take a long (>1 day) time to complete on a big FS. > > - Erik > > > > On 02/07/2011 10:21 PM, Leonidas Spyropoulos wrote: > > Hey all, > > > > I run into no space left on device on a virtualbox > > > > After installing Debian 6 on a virtual machine > > I tried installing the KDE desktop > > > > The system HDD is 8Gb > > Both root (/) and /home are btrfs > > over LVM. > > > > While installing the packages I run into: > > > > no space left, need 4096, 4096 dealloc bytes, 1776283648 > > bytes_used, 0 bytes_reserved, > > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total > > > > df shows only 74% used space on / > > > > kernel used: stock debian 6 2.6.32-5-686 > > > > At the moment I cannot access it with normal boot, only recovery > > mode. > > > > I can provide whatever info you would like as long as you think of a > > way to load the normal system and not the recovery mode. > > > > > > > > > > -- > 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-- 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
On Mon, Feb 7, 2011 at 3:21 PM, Leonidas Spyropoulos <artafinde@gmail.com> wrote:> Hey all, > > I run into no space left on device on a virtualbox > > After installing Debian 6 on a virtual machine > I tried installing the KDE desktop > > The system HDD is 8Gb > Both root (/) and /home are btrfs > over LVM. > > While installing the packages I run into: > > no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0 > bytes_reserved, > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total > > df shows only 74% used space on / > > kernel used: stock debian 6 2.6.32-5-686 > > At the moment I cannot access it with normal boot, only recovery mode. > > I can provide whatever info you would like as long as you think of a > way to load the normal system and not the recovery mode.IIRC .32 has all sorts of ENOSPC problems; I think this was seriously tackled in kernels > .32... this kernel was only declared ready for "early adopters", with an "expect issues" disclaimer. The btrfs-tools in squeeze is probably so old you may not even have the `btrfs` binary, but I don''t run debian so I''m not sure there... not really a solution probably for you, but I wouldn''t run that kernel if using btrfs. C Anthony -- 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
On Feb 8, 2011 12:09 AM, "C Anthony Risinger" <anthony@extof.me> wrote:> > On Mon, Feb 7, 2011 at 3:21 PM, Leonidas Spyropoulos > <artafinde@gmail.com> wrote: > > Hey all, > > > > I run into no space left on device on a virtualbox > > > > After installing Debian 6 on a virtual machine > > I tried installing the KDE desktop > > > > The system HDD is 8Gb > > Both root (/) and /home are btrfs > > over LVM. > > > > While installing the packages I run into: > > > > no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0 > > bytes_reserved, > > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total > > > > df shows only 74% used space on / > > > > kernel used: stock debian 6 2.6.32-5-686 > > > > At the moment I cannot access it with normal boot, only recovery mode. > > > > I can provide whatever info you would like as long as you think of a > > way to load the normal system and not the recovery mode. > > IIRC .32 has all sorts of ENOSPC problems; I think this was seriously > tackled in kernels > .32... this kernel was only declared ready for > "early adopters", with an "expect issues" disclaimer. > > The btrfs-tools in squeeze is probably so old you may not even have > the `btrfs` binary, but I don''t run debian so I''m not sure there... > not really a solution probably for you, but I wouldn''t run that kernel > if using btrfs. > > C AnthonyHey all, Thanks for all the answers. The problem is that I cannot login to the system.only recovery mode works, and there btrfs command is not there as you imagined. I will try though ssh but I don''t think it''s installed by default and I cannot install it. So the next step is try from recovery console of debian live cd, which still has the really old tools... I think this is quite some serious issue but generally all debian''s fault adopting a btrfs file system support on a 2.6.32 kernel and without btrfs-progs on some decent version. I''ll update when possible. Please throw any other alternatives my way anyone. Thanks, Leonidas -- Caution: breathing may be hazardous to your health. -- 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
On Tue, Feb 8, 2011 at 3:00 AM, Leonidas Spyropoulos <artafinde@gmail.com> wrote:> On Feb 8, 2011 12:09 AM, "C Anthony Risinger" <anthony@extof.me> wrote: >> >> On Mon, Feb 7, 2011 at 3:21 PM, Leonidas Spyropoulos >> <artafinde@gmail.com> wrote: >> > Hey all, >> > >> > I run into no space left on device on a virtualbox >> > >> > After installing Debian 6 on a virtual machine >> > I tried installing the KDE desktop >> > >> > The system HDD is 8Gb >> > Both root (/) and /home are btrfs >> > over LVM. >> > >> > While installing the packages I run into: >> > >> > no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0 >> > bytes_reserved, >> > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total >> > >> > df shows only 74% used space on / >> > >> > kernel used: stock debian 6 2.6.32-5-686 >> > >> > At the moment I cannot access it with normal boot, only recovery mode. >> > >> > I can provide whatever info you would like as long as you think of a >> > way to load the normal system and not the recovery mode. >> >> IIRC .32 has all sorts of ENOSPC problems; I think this was seriously >> tackled in kernels > .32... this kernel was only declared ready for >> "early adopters", with an "expect issues" disclaimer. >> >> The btrfs-tools in squeeze is probably so old you may not even have >> the `btrfs` binary, but I don''t run debian so I''m not sure there... >> not really a solution probably for you, but I wouldn''t run that kernel >> if using btrfs. >> >> C Anthony > > Hey all, > > Thanks for all the answers. > > The problem is that I cannot login to the system.only recovery mode works, > and there btrfs command is not there as you imagined. > > I will try though ssh but I don''t think it''s installed by default and I > cannot install it. > > So the next step is try from recovery console of debian live cd, which still > has the really old tools... > > I think this is quite some serious issue but generally all debian''s fault > adopting a btrfs file system support on a 2.6.32 kernel and without > btrfs-progs on some decent version. > > I''ll update when possible. > Please throw any other alternatives my way anyone.I have to be blunt, blaming your problems on debian isn''t terribly classy. The "oooo, shiny!" reflex is your fault, not debian''s. Download and install a prebuilt 2.6.35 or later kernel into your /boot via a livecd or whatever, unpack and add the btrfs command to the initramfs for that kernel, boot up into that initramfs with the kernel option "break=premount", and fix the rootfs from the busybox prompt. Alternatively, an ubuntu natty alpha livecd has a 2.6.38 kernel, and you can install mostly up-to-date btrfs tools into that environment. I''m sure debian has something similar available. --Carey Underwood -- 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
On 8 February 2011 09:31, cwillu <cwillu@cwillu.com> wrote:> On Tue, Feb 8, 2011 at 3:00 AM, Leonidas Spyropoulos > <artafinde@gmail.com> wrote: >> On Feb 8, 2011 12:09 AM, "C Anthony Risinger" <anthony@extof.me> wrote: >>> >>> On Mon, Feb 7, 2011 at 3:21 PM, Leonidas Spyropoulos >>> <artafinde@gmail.com> wrote: >>> > Hey all, >>> > >>> > I run into no space left on device on a virtualbox >>> > >>> > After installing Debian 6 on a virtual machine >>> > I tried installing the KDE desktop >>> > >>> > The system HDD is 8Gb >>> > Both root (/) and /home are btrfs >>> > over LVM. >>> > >>> > While installing the packages I run into: >>> > >>> > no space left, need 4096, 4096 dealloc bytes, 1776283648 bytes_used, 0 >>> > bytes_reserved, >>> > 0 bytes_pinned, 0 bytes_readonly, 0 may use 1776287744 total >>> > >>> > df shows only 74% used space on / >>> > >>> > kernel used: stock debian 6 2.6.32-5-686 >>> > >>> > At the moment I cannot access it with normal boot, only recovery mode. >>> > >>> > I can provide whatever info you would like as long as you think of a >>> > way to load the normal system and not the recovery mode. >>> >>> IIRC .32 has all sorts of ENOSPC problems; I think this was seriously >>> tackled in kernels > .32... this kernel was only declared ready for >>> "early adopters", with an "expect issues" disclaimer. >>> >>> The btrfs-tools in squeeze is probably so old you may not even have >>> the `btrfs` binary, but I don''t run debian so I''m not sure there... >>> not really a solution probably for you, but I wouldn''t run that kernel >>> if using btrfs. >>> >>> C Anthony >> >> Hey all, >> >> Thanks for all the answers. >> >> The problem is that I cannot login to the system.only recovery mode works, >> and there btrfs command is not there as you imagined. >> >> I will try though ssh but I don''t think it''s installed by default and I >> cannot install it. >> >> So the next step is try from recovery console of debian live cd, which still >> has the really old tools... >> >> I think this is quite some serious issue but generally all debian''s fault >> adopting a btrfs file system support on a 2.6.32 kernel and without >> btrfs-progs on some decent version. >> >> I''ll update when possible. >> Please throw any other alternatives my way anyone. > > I have to be blunt, blaming your problems on debian isn''t terribly > classy. The "oooo, shiny!" reflex is your fault, not debian''s.Well you are right it is my problem and yeah I wanted to test the "new shiny" Debian 6 with officially btrfs supported. For the moment I apt-get clean to get some space since my / was updating the KDE (so it had a lot of cache files there) Reserved something like 300Mb and then vlextend the / But the next step is to update kernel and btrfs-progs from git. Thanks for answers> > Download and install a prebuilt 2.6.35 or later kernel into your /boot > via a livecd or whatever, unpack and add the btrfs command to the > initramfs for that kernel, boot up into that initramfs with the kernel > option "break=premount", and fix the rootfs from the busybox prompt.The above seems unknown to me. Could you elaborate a bit please?> > Alternatively, an ubuntu natty alpha livecd has a 2.6.38 kernel, and > you can install mostly up-to-date btrfs tools into that environment. > I''m sure debian has something similar available.I was wondering how to fix this without liveCD.> > --Carey Underwood >-- Caution: breathing may be hazardous to your health. -- 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
Hallo, Leonidas, Du meintest am 08.02.11: [...]>> I have to be blunt, blaming your problems on debian isn''t terribly >> classy. The "oooo, shiny!" reflex is your fault, not debian''s.> Well you are right it is my problem and yeah I wanted to test the > "new shiny" Debian 6 with officially btrfs supported.It''s my problem too - I have to restore about 1.5 TByte somehow ...> For the moment I apt-get clean to get some space since my / was > updating the KDE (so it had a lot of cache files there) > Reserved something like 300Mb and then vlextend the /> But the next step is to update kernel and btrfs-progs from git.Maybe that doesn''t help now. I''m working with kernel 2.6.37 and kernel 2.6.38-rc2, and I''ve got big problems. Viele Gruesse! Helmut -- 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
>> But the next step is to update kernel and btrfs-progs from git. > > Maybe that doesn''t help now. I''m working with kernel 2.6.37 and kernel > 2.6.38-rc2, and I''ve got big problems.I had to install at least 2.6.37 to have a kernel with an advanced enough balance feature to actually reclaim the free space and report it correctly too. Still, I had so much kernel crashes during this balance operation that even after numerous retries I still hadn''t once completed it (on a FS of merely 300GB). Fortunately Zheng Yan coded a patch, which I applied to 2.6.38-rc2, so that I could finally run - and finish - the balance operation. Additionally this version of btrfs is more clever in not wasting the free space to begin with, hence making future rebalances for reclaiming free space no longer necessary. That patch is released on this list on january 26th, called "Fix balance panic". If you experience the same, you could try applying this patch too. There is no (pre-built) kernel yet with this patch already applied. - Erik. -- 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
Hallo, Erik, Du meintest am 08.02.11:>>> But the next step is to update kernel and btrfs-progs from git.>> Maybe that doesn''t help now. I''m working with kernel 2.6.37 and >> kernel 2.6.38-rc2, and I''ve got big problems.[...]> Fortunately Zheng Yan coded a patch, which I > applied to 2.6.38-rc2, so that I could finally run - and finish - the > balance operation.[...]> That patch is released on this list on january 26th, called "Fix > balance panic". If you experience the same, you could try applying > this patch too. There is no (pre-built) kernel yet with this patch > already applied.Maybe it will help. But my actual problem is: I cannot mount the btrfs system (it leads to "kernel panic"). And starting "btrfs filesystem balance ..." requires a mounted btrfs system. I''ll see ... Viele Gruesse! Helmut -- 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
Hallo, Erik, Du meintest am 08.02.11: [...]> Fortunately Zheng Yan coded a patch, which I > applied to 2.6.38-rc2, so that I could finally run - and finish - the > balance operation. > Additionally this version of btrfs is more clever in not wasting the > free space to begin with, hence making future rebalances for > reclaiming free space no longer necessary.That patch isn''t yet included in 2.6.38-rc4. Viele Gruesse! Helmut -- 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
Hallo, Erik, Du meintest am 08.02.11:>> Maybe that doesn''t help now. I''m working with kernel 2.6.37 and >> kernel 2.6.38-rc2, and I''ve got big problems.> I had to install at least 2.6.37 to have a kernel with an advanced > enough balance feature to actually reclaim the free space and report > it correctly too. > Still, I had so much kernel crashes during this balance operation > that even after numerous retries I still hadn''t once completed it (on > a FS of merely 300GB). Fortunately Zheng Yan coded a patch, which I > applied to 2.6.38-rc2, so that I could finally run - and finish - the > balance operation.Didn''t help - sorry. You can take a look to the last lines of my system after crashing into "kernel panic" with blinkenlights: http://helmut.hullen.de/btrfs/ The screenshots are hard to read - sorry. Viele Gruesse! Helmut -- 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
>> That patch is released on this list on january 26th, called "Fix >> balance panic". If you experience the same, you could try applying >> this patch too. There is no (pre-built) kernel yet with this patch >> already applied. > > Maybe it will help. But my actual problem is: I cannot mount the btrfs > system (it leads to "kernel panic"). And starting "btrfs filesystem > balance ..." requires a mounted btrfs system.Yeah sorry, I hadn''t noticed that. No, that patch will certainly not fix a filesystem you can''t mount to begin with. Can''t help you out. - Erik -- 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