On 2016-02-01 15:21, Hugo Mills wrote:
On Mon, Feb 01, 2016 at 02:44:24PM -0500, Austin S. Hemmelgarn wrote:
In the process of trying to debug issues I'm having on one of my
systems with a new kernel version, I decided to do a dry run check on
the root filesystem. 'btrfs check' returned a bunch
Hi,
df on btrfs RAID1 fs on 3 disks (they are RAID0 hardware, two disk,
arrays but its not important right?) show wrong avail space when empty
# uname -a
Linux kvm4.prisma 4.4.0-2.el7.elrepo.x86_64 #1 SMP Tue Jan 26 13:06:01
EST 2016 x86_64 x86_64 x86_64 GNU/Linux
# btrfs --version
btrfs-pr
On Tue, Feb 02, 2016 at 03:16:40PM +0100, Marco Lorenzo Crociani wrote:
> Hi,
> df on btrfs RAID1 fs on 3 disks (they are RAID0 hardware, two disk,
> arrays but its not important right?) show wrong avail space when
> empty
>
> # uname -a
> Linux kvm4.prisma 4.4.0-2.el7.elrepo.x86_64 #1 SMP Tue Ja
On Tue, Feb 02, 2016 at 12:43:45AM +0100, David Sterba wrote:
> Hi,
>
> On Wed, Jan 20, 2016 at 01:49:24PM -0800, Mark Fasheh wrote:
> > A git tree of the patches can be found here:
> >
> > https://github.com/markfasheh/btrfs-progs-patches/tree/du
>
> what changed since the previous posting?
No
Hi all! I have problem with hanging btrfs file system.
[17047.652816] INFO: task btrfs-cleaner:770 blocked for more than 120 seconds.
[17047.652837] Not tainted 4.3.5-300.fc23.x86_64+debug #1
[17047.652853] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[17047.6528
Hello Chris,
That's a bit weird. This is BIOS or UEFI system? On UEFI, the prebaked
grubx64.efi includes btrfs, so insmod isn't strictly needed. But on
BIOS it would be.
it is a Virtual-Box-VM. It is a BIOS system
> It might be as simple as manually mounting:
>btrfs dev scan
>btrfs fi show
##
Hello Hugo,
>> Here I am stuck in a recovery prompt.
By far the simplest and most reliable method of doing this is to
use an initramfs with the command "btrfs dev scan" in it somewhere
before mounting. Most of the major distributions already have an
initramfs set up (as does yours, I see), a
On Tue, Feb 2, 2016 at 2:59 PM, Hendrik Friedel wrote:
> Hello Chris,
>
>> That's a bit weird. This is BIOS or UEFI system? On UEFI, the prebaked
>> grubx64.efi includes btrfs, so insmod isn't strictly needed. But on
>> BIOS it would be.
>
> it is a Virtual-Box-VM. It is a BIOS system
>
>> It migh
On Tue, Feb 2, 2016 at 3:01 PM, Hendrik Friedel wrote:
> Hello Hugo,
>
>>> Here I am stuck in a recovery prompt.
>>
>> By far the simplest and most reliable method of doing this is to
>> use an initramfs with the command "btrfs dev scan" in it somewhere
>> before mounting. Most of the major di
On Tue, Feb 02, 2016 at 11:01:38PM +0100, Hendrik Friedel wrote:
> Hello Hugo,
>
> >> Here I am stuck in a recovery prompt.
> >By far the simplest and most reliable method of doing this is to
> >use an initramfs with the command "btrfs dev scan" in it somewhere
> >before mounting. Most of the
[ adding btrfs, resend with the correct list address ]
On Tue, Feb 2, 2016 at 3:19 PM, Al Viro wrote:
> On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wrote:
>
>> However, for raw block devices and for XFS with a real-time device, the
>> value in inode->i_sb->s_bdev is not correct. With
On Tue, Feb 02, 2016 at 03:39:15PM -0800, Dan Williams wrote:
> On Tue, Feb 2, 2016 at 3:19 PM, Al Viro wrote:
> > On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wrote:
> >> However, for raw block devices and for XFS with a real-time device, the
> >> value in inode->i_sb->s_bdev is not cor
On Wed, Feb 03, 2016 at 01:20:22AM +0500, Михаил Гаврилов wrote:
> Hi all! I have problem with hanging btrfs file system.
It's not clear that who held the lock, any luck to find clues in
sysrq+w?
Thanks,
-liubo
>
> [17047.652816] INFO: task btrfs-cleaner:770 blocked for more than 120 seconds.
>
On Tue, Feb 2, 2016 at 1:20 PM, Михаил Гаврилов
wrote:
> Hi all! I have problem with hanging btrfs file system.
Can you list the workload at the time, and also the mount options? To
do sysrq+w as Liu Bo asks for, do this:
echo 1 > /proc/sys/kernel/sysrq
echo w > /proc/sysrq-trigger
And then 'j
On Tue, Feb 2, 2016 at 8:52 PM, Михаил Гаврилов
wrote:
> 2016-02-03 7:45 GMT+05:00 Chris Murphy :
>> journalctl -k > kernel-sysrqw_btrfscleaner770blocked.txt
>
>
> This I can do now or after next hang?
The sysrq+w should happen when the hang is happening. This dumps
hanged task info to kernel mes
Mike: From your attachment, looks like you rebooted. So do this:
echo 1 > /proc/sys/kernel/sysrq
Reproduce the problem where you get blocked task messages in dmesg
echo w > /proc/sysrq-trigger
journalctl -k > kernel-sysrqw-btrfscleaner770blocked-2.txt
Make sure you use the same mount options. Lo
CURRENT_TIME macro is not appropriate for filesystems as it
doesn't use the right granularity for filesystem timestamps.
Use current_fs_time() instead.
Signed-off-by: Deepa Dinamani
Cc: Chris Mason
Cc: Josef Bacik
Cc: David Sterba
Cc: linux-btrfs@vger.kernel.org
---
fs/btrfs/file.c|
Hello,
I would like to go the sensible way :-)
But can you hint me how and where to add the btrfs device scan option to the
initramfs?
If btrfs-progs 4.3.1 is installed already, dracut -f will rebuild the
initramfs and should just drag in current tools which will include
'btrfs device scan'.
18 matches
Mail list logo