• 0

Btrfs Status?


Question

Recommended Posts

  • 0
The executable is in /usr/syno/bin/scemd (my fault)

 

I added the support_dr_snap="yes" to the /etc.defaults/synoinfo.conf

I get the Data Protection Manager now. It is a GUI for managing iscsi LUN snapshots. That was not what I was looking for: a GUI for managing BTRFS snapshots.

 

the gui is the same for managing the snapshots.

 

i added the lines in synoinfo.conf but it keeps crashing when i try to create a new volume and disk group, how did you manage to create it?

Link to post
Share on other sites
  • 0

I added the entries support_btrfs="yes" and support_dr_snap="yes" to both /etc/synoinfo.conf and /etc.defaults/synoinfo.conf (just to be sure)

I do not use disk groups.

 

I tried it on a real DS1813+ where I could create a btrfs volume on multiple disks and allocate shares on it. I can create and delete directories from filemanager From the cli I can take snapshots and delete them (not from the gui.)

 

On a virtualbox instance I created an ext4 volume (volume2). After that I used the cli to look up where volume2 was mounted. (in my case /dev/vg1001/lv) I removed volume2 and recreated it as a btrfs file system in storage manager. (Storage Manager completes with a message that volume2 is crashed.)

A manual mount "mount /dev/vg1001/lv /volume2" from the cli does the trick. (the manual mount has to be repeated after every reboot of the VB DSM instance)

 

The DS1813+ btrfs volume mounts automatically after a reboot of the system.

Link to post
Share on other sites
  • 0

From a VirtualBox DSM system:

 

Storage Manager -> Create Volume

 

Choose all options you would like to use on the designated btrfs volume.

Create the volume with "Traditional volume format (ext4)

 

After the creation of the new volume, enter the CLI and type:

 

mount | grep volume

 

It will give you the devicenames of all volumes, including the freshly created one.

in my case:

 

/dev/vg1001/lv on /volume2 type ext4 (usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl)

 

make a note of the device name (your's could be different)

 

Now remove the newly created volume from the storage manager and recreate the volume with a btrfs filesystem. (It is important to keep all other settings in the creation process the same. You might end up with a different devicename and corrupt data on other volumes when mounting)

 

The creation process will end with a "Crashed" message.

 

In the CLI enter:

 

mount

 

in my case:

 

mount /dev/vg1001/lv /volume2

 

In the storage manager the crashed Volume will return to a "Normal" status and can be used now.

 

After every reboot the btrfs volume has to be manually mounted. (This is due to the workarounds in XPenology. On a DS1813+ it mounts automatically after creation and the volume survives reboots.)

 

The brtfs-volume can be managed from the cli (btrfs --help comes to the rescue)

I do not recommend tinkering with disks like adding or removing disks to/from the volume. It could confuse DSM, ending in system corruption

 

A share on the btrfs volume is a btrfs subvolume and can be managed from the CLI, including snapshotting.

Link to post
Share on other sites
  • 0

i managed to get the same results but it's not fully working.. here is my recap:

 

1. first thing, upgrading 5.2-5592 to update3 brings some new stuff to btrfs.ko i think

 

zC908CR.png

 

2. volume creation works but mount is crashing at boot, manually mount makes volume online again.

 

NKGPnsy.png

 

3. shr expansion works adding a disk and btrfs filesystem grows so handlig here is ok

 

3slpDi6.png

 

4. data protection is enabled while creating a new share in the volume (i suppose it's snapshot ability)

 

KzCW9i6.png

 

5. folder is visible as it should in file manager and #snapshot is here too

 

x95xRfD.png

 

6. data protection manager handles the share snapshots and let you manually snap or schedule it

 

2DjN3tC.png

 

7. creating the first snapshot gives error to all users (even SYSTEM)

 

N7oJzkb.png

 

 

 

i wanted to try to make via ssh a manual snapshot and see if DPM handles it but i'm stuck with it :\

Link to post
Share on other sites
  • 0

The snapshot and advanced data protection items don't show up in my DSM.

What are your modifications to /etc/synoinfo.conf and /etc.defaults/synoinfo.conf (or other settings files?)

 

I found I had forgotten to make the entries support_share_snapshot in the synoconfig files.

 

The snapshots fail because of apparmor. The dmesg entry:

 

type=1400 audit(1441125222.962:2): apparmor="DENIED" operation="mkdir" parent=15715 profile="/usr/syno/synoman/webman/index.cgi" name="/usr/syno/synoman/synohdpack/tmp/" pid=15749 comm="mkdir" requested_mask="c" denied_mask="c" fsuid=0 ouid=0

 

What is the way to add a definition to apparmor?

Edited by Guest
Link to post
Share on other sites
  • 0

With the entries

 

support_btrfs="yes"

support_dr_snap="yes"

support_share_snapshot="yes"

 

in /etc/synoinfo.conf and /etc.default/synoinfo.conf the btrfs filesystem works and supports snapshotting on my ds1813+

 

I think with some further modifications in the XPenology workarounds it could be enabled there too!

Link to post
Share on other sites
  • 0
With the entries

 

support_btrfs="yes"

support_dr_snap="yes"

support_share_snapshot="yes"

 

in /etc/synoinfo.conf and /etc.default/synoinfo.conf the btrfs filesystem works and supports snapshotting on my ds1813+

 

I think with some further modifications in the XPenology workarounds it could be enabled there too!

 

excellent :smile: maybe next release of xpenology could bring us a fix :smile:

Link to post
Share on other sites
  • 0
With the entries

 

support_btrfs="yes"

support_dr_snap="yes"

support_share_snapshot="yes"

 

in /etc/synoinfo.conf and /etc.default/synoinfo.conf the btrfs filesystem works and supports snapshotting on my ds1813+

 

I think with some further modifications in the XPenology workarounds it could be enabled there too!

 

excellent :smile: maybe next release of xpenology could bring us a fix :smile:

With the entries

 

support_btrfs="yes"

support_dr_snap="yes"

support_share_snapshot="yes"

 

in /etc/synoinfo.conf and /etc.default/synoinfo.conf the btrfs filesystem works and supports snapshotting on my ds1813+

 

I think with some further modifications in the XPenology workarounds it could be enabled there too!

 

The best is probably a XPenoboot boot based on the new Synology product RS18016xs+ We will see i hope the developers of xpenoboot will make btrfs workable for use at xpenology NAS systems.

Link to post
Share on other sites
  • 0

i don't think the problem needs another rebase of xpenology, the genuine ds3615xs is probably working fine with btrfs like benji30's ds1813+ out of the box with some modification at the *.conf and i think with the next big update Synology will bring btrfs to all latest gen NAS.

Link to post
Share on other sites
  • 0

looking forward for official Xpenology BTRFS support, it is a really nice filesystem I've seen an implementation in rockstor.com and it is starting to shape up, with the advanced applications and usability of DSM and that excellent filesystem we would have a very resilient NAS.

Link to post
Share on other sites
  • 0

I have a spare machine with 2 x 4TB disks, just tried with 5592 Update 4 (direct update from UI, it works!)

It has a /dev/md2 device (mirror), same as previous posts, the volume crashed immediately, mounting it to /volume1/ by command and then it works.

I've chosen "enable enhanced data integrity" in options but no idea how it can enhance data integrity.

 

And I tried to transfer about 10GB files from my PC using FTP, everything looks good, we just need a way to figure out how to automount it during reboot.

Link to post
Share on other sites
  • 0
The snapshot and advanced data protection items don't show up in my DSM.

What are your modifications to /etc/synoinfo.conf and /etc.defaults/synoinfo.conf (or other settings files?)

 

I found I had forgotten to make the entries support_share_snapshot in the synoconfig files.

 

The snapshots fail because of apparmor. The dmesg entry:

 

type=1400 audit(1441125222.962:2): apparmor="DENIED" operation="mkdir" parent=15715 profile="/usr/syno/synoman/webman/index.cgi" name="/usr/syno/synoman/synohdpack/tmp/" pid=15749 comm="mkdir" requested_mask="c" denied_mask="c" fsuid=0 ouid=0

 

What is the way to add a definition to apparmor?

 

 

I have the same logs too. THis gets written to the kern.log every minute. any one know how to disable this? I am running xepnology 5.2 5592 Update4, under virtualbox.

Link to post
Share on other sites
  • 0
this (btrfs) is basicly the one thing that would make xpenology perfect at this stage :smile:

has there been any comments anywhere else anyone knows of about the current state of btrfs?

 

Most users when talking about BTRFS they usually care about following things: data integrity protection (bit rod protection), snapshots and integrated volume management.

 

The volume in DSM is built on top of disk group, which takes care of redundancy. That nullifies the BTRFS-integrated volume management and ability to add/remove devices from the volume. DSM comes with SHR, which provides some of those features too - but not as flexible as BTRFS.

 

A slightly different way of defining volumes would need to be introduced to leverage BTRFS here. Additional options for RAID level when would work great: one would create a BTRFS diskgroup and volumes inside it - implemented as BTRFS subvolumes. Creating a BTRFS volume on top of RAID diskgroup does not bring many features, except for immediate snapshots. This has however one disadvantage - one cannot create effective LUNs on top of such BTRFS diskgroup...

 

So, currently BTRFS sees only one block device. Now, if one wants to guarantee the integrity, a RAID1 profile for both data and metadata would have to be used in BTRFS, reducing the usable capacity by 50% - all on top of already redundant raid. Unfortunately BTRFS does know nothing about the underlying hardware, so it cannot utilize it more efficiently.

 

Snapshots are still there, regardless of the underlying layer.

 

So, it seems the support for BTRFS in 5.2 does not make much sense at the moment. I trust that DSM 6.0 will come with much more comprehensive support, with post 3.19 kernel as well.

Link to post
Share on other sites
  • 0

Thank you so much for your advice!

 

I successfully set a btrfs volume following your guide.

 

However, the volume does not accept uploaded files via windows network (SMB)

with the message that there is not enough space(actually I dont know the exact message because

I use korean language).

 

This problem does not appear when I create a volume as ext4!

 

Do you have any suggestion for this?

Thank you in advance.

Link to post
Share on other sites
  • 0

Hello,

 

I also create a working Xpenology DSM 6 with actual Pat File on an normal Intel machine.

 

Same procedure - after reboot - the volume crashed and I fix this with the task manager, running a task as root with "mount /dev/mapper-vg1 /volume1" and the crashed volume will become GOOD.

 

But all the "Shared Folders" are not present - via SSH I can see all the "subvolumes" and all the files in it.

 

At the moment, when I reboot the machine, I create the shared folders (same name and para) via the WEB ui again and all my files become present.

 

Is is possible to mount also the subvolumes as "Shared Folders" with a mount or btrfs command?

Link to post
Share on other sites
  • 0

 

Is is possible to mount also the subvolumes as "Shared Folders" with a mount or btrfs command?

 

 

 

Have you figured this out yet? This is exactly the point I'm at as well. I need a command that will create the missing shares at reboot to create a seamless experience with DSM 6 on baremetal.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.