Chris Mason wrote (ao):
I'm happy to patch up bugs in the FS (or point you to newer
kernels that have them fixed) but at this point we don't have enough
info to say if it is an FS problem or a debian package problem.
Perhaps if you ran it under strace?
Other distros don't have problems
The btrfs wiki Main Page warns that it is currently possible to corrupt
a filesystem irrecoverably if your machine crashes or loses power on disks
that don't handle flush requests correctly.
How do you know if this applies to your drives? Is there a way to test it,
or a model list, or are newer
On Thursday 5 May, 2011 23:33:33 Sander wrote:
Can you do:
echo true /var/lib/dpkg/info/grub-installer.postinst
and try again?
At some point somehow grup-pc apparently got installed, even with the script
failure. So I tried my dist-upgrade again, and seems to have completed almost
400
cac...@quantum-sci.com wrote (ao):
On Thursday 5 May, 2011 23:33:33 Sander wrote:
Can you do:
echo true /var/lib/dpkg/info/grub-installer.postinst
and try again?
At some point somehow grup-pc apparently got installed, even with the
script failure. So I tried my dist-upgrade
On 05/05/2011 10:36 PM, liubo wrote:
The current code relogs the entire inode every time during fsync log,
and it is much better suited to small files rather than large ones.
During my performance test, the fsync performace of large files sucks,
and we can ascribe this to the tremendous amount
On Friday 6 May, 2011 05:20:28 Sander wrote:
Can you post the error?
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully
On 05/06/2011 05:13 AM, Paul Schroeder wrote:
The btrfs wiki Main Page warns that it is currently possible to corrupt
a filesystem irrecoverably if your machine crashes or loses power on disks
that don't handle flush requests correctly.
How do you know if this applies to your drives? Is there a
cac...@quantum-sci.com wrote (ao):
On Friday 6 May, 2011 05:20:28 Sander wrote:
Can you post the error?
Do you want to continue [Y/n]?
Setting up linux-image-2.6.38-2-amd64 (2.6.38-3) ...
/usr/sbin/grub-probe: error: cannot stat `/dev/root'.
run-parts:
Hallo, Cacook,
Du meintest am 06.05.11:
I can't reboot at this point, as on this machine I started a
'balance' through ssh on another machine, and it's been running for
over 12 hours. It does not respond to ^C and I'm afraid to reboot
with it running.
That's a behaviour which was described
Excerpts from Josef Bacik's message of 2011-05-06 09:10:23 -0400:
On 05/06/2011 05:13 AM, Paul Schroeder wrote:
The btrfs wiki Main Page warns that it is currently possible to corrupt
a filesystem irrecoverably if your machine crashes or loses power on disks
that don't handle flush requests
Same old problem.
On Friday 6 May, 2011 06:21:58 Sander wrote:
Can you try:
dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb
apt-get dist-upgrade
# dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb
(Reading database ... 135273 files and directories currently
cac...@quantum-sci.com wrote (ao):
# dpkg -i /var/cache/apt/archives/grub-pc_1.99~rc1-13_amd64.deb
(Reading database ... 135273 files and directories currently installed.)
Preparing to replace grub-pc 1.99~rc1-13 (using
.../grub-pc_1.99~rc1-13_amd64.deb) ...
Unpacking replacement grub-pc ...
On Friday 6 May, 2011 07:17:00 you wrote:
Hm. Just do cp /bin/true /usr/sbin/grub-probe
Yikes, it came up with an ncurses screen saying:
GRUB failed to install to the following devices:
│
│
Excerpts from liubo's message of 2011-05-05 22:36:09 -0400:
The current code relogs the entire inode every time during fsync log,
and it is much better suited to small files rather than large ones.
During my performance test, the fsync performace of large files sucks,
and we can ascribe
On Friday 6 May, 2011 07:58:47 you wrote:
Say 'yes', try to finish your upgrade.
Now when I ran it, it went as normal for some reason.
Then:
grub-install /dev/sda
Auto-detection of a filesystem of failed.
Please report this together with the output of /usr/sbin/grub-probe
On Friday 6 May, 2011 08:15:25 cac...@quantum-sci.com wrote:
I'm afraid to reboot though, because yesterday I started a btrfs fi balance
on this machine while sshed to another, and that is still running 15 hours
later with no indication of progress nor sign of abating. ^C is ineffective.
Anyone here?
On Friday 6 May, 2011 10:09:29 cac...@quantum-sci.com wrote:
On Friday 6 May, 2011 08:15:25 cac...@quantum-sci.com wrote:
I'm afraid to reboot though, because yesterday I started a btrfs fi balance
on this machine while sshed to another, and that is still running 15 hours
On Fri, May 06, 2011 at 01:04:28PM -0700, cac...@quantum-sci.com wrote:
Anyone here?
Could you create link from you root parition to /dev/root and try again?
--
Tomasz Torcz Morality must always be based on practicality.
xmpp: zdzich...@chrome.pl-- Baron
cac...@quantum-sci.com wrote (ao):
Wow. I was very nearly completely screwed. I went ahead and
rebooted, but grub.cfg was not set up at all. I had no way to run
update-grub on that root, and so tried manually filling in the
missing parameters. That didn't work, probably through the
cac...@quantum-sci.com wrote:
I don't understand this.
Clearly. Please continue the discussion in a debian or grub forum..
It really has nothing to do with btrfs.
//Peter
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to
On Friday 6 May, 2011 13:51:37 Peter Stuge wrote:
cac...@quantum-sci.com wrote:
I don't understand this.
Clearly. Please continue the discussion in a debian or grub forum..
It really has nothing to do with btrfs.
No thanks. This is a BTRFS problem, and if you people don't want to face it,
cac...@quantum-sci.com wrote:
# update-grub
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
# update-grub -v
grub-mkconfig (GRUB) 1.99~rc1-13
#
It's still BTRFS incompatibility.
Either that, or maybe something has broken in your many attempts to
solve the
cac...@quantum-sci.com wrote:
Clearly. Please continue the discussion in a debian or grub forum..
It really has nothing to do with btrfs.
No thanks. This is a BTRFS problem, and if you people don't want to
face it, that's fine.
A problem that happens when you use btrfs is not
On Fri, May 06, 2011 at 02:20:48PM -0700, cac...@quantum-sci.com wrote:
I'm tearing out BTRFS and using another filesystem.
I think this is probably a good conclusion for you. I would
strongly suggest you pick something reliable (like ext3 or ext4) for
your future needs. Picking an
Hugo Mills wrote:
On Fri, May 06, 2011 at 02:20:48PM -0700, cac...@quantum-sci.com wrote:
I'm tearing out BTRFS and using another filesystem.
I think this is probably a good conclusion for you. I would
strongly suggest you pick something reliable (like ext3 or ext4) for
your future
On May 6, 2011 4:20 PM, cac...@quantum-sci.com wrote:
On Friday 6 May, 2011 13:51:37 Peter Stuge wrote:
cac...@quantum-sci.com wrote:
I don't understand this.
Clearly. Please continue the discussion in a debian or grub forum..
It really has nothing to do with btrfs.
No thanks. This
On Fri, May 6, 2011 at 8:51 PM, C Anthony Risinger anth...@extof.me wrote:
On May 6, 2011 4:20 PM, cac...@quantum-sci.com wrote:
On Friday 6 May, 2011 13:51:37 Peter Stuge wrote:
cac...@quantum-sci.com wrote:
I don't understand this.
Clearly. Please continue the discussion in a debian
27 matches
Mail list logo
