benji30

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 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?

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.

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.

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.

Replacing the /usr/syno/bin/cemd executable in my 1813+ with the one from the 18016 made my 1813+ instantly panic. I don't recommend replacing this. No Data Protection Manager in the menu of my DS1813+ despite the mods in synoinfo.conf When I created my first BTFRS filesystem the volume crashed too. I solved this at first by recreating the BTRFS volume (remove / create) from the cli find the mountpoint of the BTRFS volume (which was /mnt/md3 in my system) your's could be different. After reboot I was able to manual mount the BTRFS disk

I borked my installation by replacing the cemd in my 1813+ with the one from the 18016+ (the file was bigger so I supposed it contains the snapshot GUI) In fact the DSM panicked and disabled all access to the system. After a reboot I was only able to reinstall the DSM for the 1813+. After that, I did not lose any data or configuration. Even the BTRFS filesystem mounted without errors. (lucky me!) and still runs fine. I have the support_dr_snap="yes" in the synoinfo,conf and also the support_share_snapshot="yes". When I take a snapshot (via the cli) the snapshot is shown as a share and can be accessed. Where am I supposed to find the snapshot gui?

I created the new volume from the GUI. After selecting the RAID type it offered me the choice between ext4 or "new" btrfs filesystem. Unfortunately I don't know how or where to enable the snapshot timeline as shown in the Synology DS18016+ specifications From the screen capture on the DS18016+ specs page it is not a 100% clear whether the Data Protection Manager is a separate downloadable package or an integrated package in the DSM .PAT file. Anyone a hint where I could find anything in the .PAT file?

I added the: support_btrfs="yes" to /etc.defaults/synoinfo.conf And restarted my DS1813+. I was able to create a raid5 volume with a BTRFS filesystem. I can define shares and copy data in them. I rebooted the system and everything works OK. Apparently the BTRFS functionality is in the .PAT file. However I am not able to manage snapshots and other functionality of BTRFS from the DSM-GUI. (all CLI items seem to be present and working)