d to see rename and
delete events, too.
- btrfs subvolume find-new: As far as I know that only finds changes
between snapshots. I need something a little more real-timey, and I
have to know if the file has been changed once or several times.
As I said: I'm thankful for any hint
Is there anything else I can do? I still have the file and should be
able to provide more data if needed.
2014-05-11 8:12 GMT+02:00 Ronald :
> Forgot to mention that these btrfs partitions reside on an LVM.
>
> 2014-05-11 7:56 GMT+02:00 Ronald :
>> Dear btrfs developers,
>>
&
Forgot to mention that these btrfs partitions reside on an LVM.
2014-05-11 7:56 GMT+02:00 Ronald :
> Dear btrfs developers,
>
> Since v3.14, it has occasionally hapenned that reading some files from
> a btrfs partition cause the process to hang. Right, a file has been
> located tha
during
boot.
The bisect failed, since the attempt to boot the latest marked good
kernel ended in an OOPS. So, testing this was not reliable.
The machine is an 32bit UP box. ~10,5 years old. This bug has also
been observed on multicore 64bit machines.
Would appreciate some pointers on how to debug
Filesystem apparently got corrupted due to memory failures.
Full dmesg is here: http://pastebin.com/x8Z0P5xG
There are errors like:
[ 188.667338] btrfs: corrupt leaf, bad key order:
block=79691776,root=1, slot=50
Warning:
[ 441.746649] [ cut here ]
[ 441.746672] WARNI
Nobody? Did I not provide enough information? Outdated kernel?
2014/1/14 Ronald :
> Dear developers,
>
> I have a 1250MHZ 512MB RAM x86 UP system. It contains several btrfs
> partitions on top of LVM mounted with compress=lzo,space_cache,noatime
> and some other standard options
Dear developers,
I have a 1250MHZ 512MB RAM x86 UP system. It contains several btrfs
partitions on top of LVM mounted with compress=lzo,space_cache,noatime
and some other standard options.
It uses a trimmed custom kernel. The -dirty part in it's name is
because the command 'hostname' was not ther
Hello, .. what do I do when I get " *** Some devices missing " and " "Unable to
stat /dev/sdg" , error message after drive is hotswaped or die ?
this is what I did?
1. mkfs.btrfs -m raid1 -d raid10 -L btrfs_label_01 /dev/sda /dev/sdb /dev/sdc
/dev/sdd /dev/sdf /dev/sdg
2. mount -t btrfs -o comp
