File “/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py”, line 41, in _handle_exception
yield
File “/opt/rockstor/src/rockstor/storageadmin/views/share.py”, line 206, in post
add_share(pool, sname, pqid)
File “/opt/rockstor/src/rockstor/fs/btrfs.py”, line 701, in add_share
toggle_path_rw(root_pool_mnt, rw=True)
File “/opt/rockstor/src/rockstor/system/osi.py”, line 657, in toggle_path_rw
return run_command([CHATTR, attr, path])
File “/opt/rockstor/src/rockstor/system/osi.py”, line 227, in run_command
raise CommandException(cmd, out, err, rc)
CommandException: Error running a command. cmd = /usr/bin/chattr -i /mnt2/NASPOOL1-R5. rc = 1. stdout = [‘’]. stderr = [‘/usr/bin/chattr: Read-only file system while setting flags on /mnt2/NASPOOL1-R5’, ‘’]
@mrmojococo Welcome to the Rockstor community forum.
You have not given any info here about the pool you created, but from from: NASPOOL1-R5 I’m wondering if you have used a parity raid level, for date or metadata, i.e. either btrfs-raid5 or 6. These default to read-only in our upstream base OS of openSUSE Leap.
If this is the case the that will be why the filesystem is then read-only:
And your options are to not use a party raid or to take a look at our following HowTo:
Where we give instructions on how to use more modern kernel and filesystem subsystems that are made available by openSUSE but with the provisos indicated in that howto.