Trying Tux3; What am I doing wrong?

Wed Aug 5 13:30:32 PDT 2015

Hi Daniel,
I don't think so:
---------------------
[root at localhost tux3]# ls -l /dev/md127
brw-rw----. 1 root disk 9, 127 Aug  5 13:18 /dev/md127
[root at localhost tux3]# mkfs.xfs -f /dev/md127
meta-data=/dev/md127             isize=256    agcount=32, agsize=183133344
blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=0        finobt=0
data     =                       bsize=4096   blocks=5860267008, imaxpct=5
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal log           bsize=4096   blocks=521728, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none
[root at localhost tux3]# mount /dev/md127 /data
[10959.647493] XFS (md127): Mounting V4 Filesystem
[10959.881743] XFS (md127): Ending clean mount
[root at localhost tux3]# touch /data/foobar
[root at localhost tux3]# ls -l /data/foobar
-rw-r--r--. 1 root root 0 Aug  5 13:21 /data/foobar
[root at localhost tux3]#

The volume itself is fine.
I am guessing that the userspace tool is creating the filesystem with wrong
version number. As I said earlier, the user/ directory is missing from
hirofumi branch, and only exists in hirofumi-user branch.

Even when using a loopback device, I get the same error:
[root at localhost ~]# dd if=/dev/zero of=foobar bs=8192 count=10240
10240+0 records in
10240+0 records out
83886080 bytes (84 MB) copied, 0.060474 s, 1.4 GB/s
[root at localhost user]# ./tux3 mkfs /root/foobar
Make tux3 filesystem on /root/foobar (blocksize 4096)
Volume size = 83886080 bytes
filemap_bufvec_check: read inode 0x1 block 0x0
filemap_extent_io: extent 0x0/40 => 0
filemap_bufvec_check: read inode 0x2 block 0x0
filemap_extent_io: extent 0x0/40 => 0
countmap_add: add 2 to group 0
save_inode: save inode 0x3f
balloc_find: scan volume for 1 blocks, goal = 2
balloc_find: groupsize = 8192, topgroup = 2, threshold = 1
balloc_find: --- pass1 ---
balloc_find: group 0: start
balloc_find: goal = 2, next = 8192, skip = 0
balloc_find_range: find 1 blocks in [2/8190], segs = 0
balloc_find_range: balloc seg [2/1]
countmap_add: add 1 to group 0
save_inode: save inode 0x4
balloc_find: scan volume for 1 blocks, goal = 3
balloc_find: groupsize = 8192, topgroup = 2, threshold = 1
balloc_find: --- pass1 ---
balloc_find: group 0: start
balloc_find: goal = 3, next = 8192, skip = 0
balloc_find_range: find 1 blocks in [3/8189], segs = 0
balloc_find_range: balloc seg [3/1]
countmap_add: add 1 to group 0
tux3_logmap_io: logchain 3
(map 0x221ae30)
[0] 0/1*
(map 0x22249f0)
(map 0x2216b30)
[root at localhost user]# mount -o loop /root/foobar /mnt
[11407.269027] loop: module loaded
mount: /dev/loop0 is write-protected, mounting read-only
[11407.283110] tux3_fill_super:775: s_blocksize 4096
[root at localhost user]# ls /root/foobar  -l
-rw-r--r--. 1 root root 83886080 Aug  5 13:28 /root/foobar
[root at localhost user]#

Masoud

On Wed, Aug 5, 2015 at 1:16 PM, Daniel Phillips <
daniel.raymond.phillips at gmail.com> wrote:

> Hi Masoud,
>
> Your md device is read-only for some reason. You need to fix that, then
> try your mount. You can also make a tux3 volume on a file and mount it
> using mount ... -oloop
>
> Regards,
>
> Daniel
>
>
> On Wed, Aug 5, 2015 at 9:53 AM, Masoud Sharbiani <
> masoud.sharbiani at gmail.com> wrote:
>
>> So, hirofumi branch does not have a fs/tux3/user/ directory:
>>
>> [root at localhost linux-tux3]# git branch
>>   hirofumi
>>   hirofumi-user
>> * master
>> [root at localhost linux-tux3]# git checkout hirofumi
>> Checking out files: 100% (23904/23904), done.
>> Switched to branch 'hirofumi'
>> [root at localhost linux-tux3]# git log
>> commit 6548a36e52cdee6bb6095f0c97f304a2e0866790
>> Author: OGAWA Hirofumi <hirofumi at mail.parknet.co.jp>
>> Date:   Sat Jun 6 18:45:08 2015 +0900
>>
>>     tux3: Cleanup deferred inode allocation in evict_inode() (temporary)
>> ....
>> [root at localhost linux-tux3]# ls fs/tux3/user
>> ls: cannot access fs/tux3/user: No such file or directory
>>
>> So I switched to hirofumi-user, where a user/ exists; I used that to run
>> mkfs, and then:
>>
>> [root at localhost tux3]# mount /dev/md127 /data
>> mount: /dev/md127 is write-protected, mounting read-only
>> [  956.051872] tux3_fill_super:775: s_blocksize 4096
>>
>> So effectively, I can see my empty file system, but not actually put
>> files/directories there.
>>
>> Masoud
>>
>>
>>
>> On Tue, Aug 4, 2015 at 10:41 PM, OGAWA Hirofumi <
>> hirofumi at mail.parknet.co.jp> wrote:
>>
>>> Masoud Sharbiani <masoud.sharbiani at gmail.com> writes:
>>>
>>> > Hi guys
>>>
>>> Hi,
>>>
>>> > I've cloned the tree, and found the userspace tools in one of the
>>> branches as well.
>>> > However after tux3 mkfs, and mounting the volume, I cannot mount the
>>> volume
>>> > read/write to actually write to it.
>>> >
>>> > What gives?
>>> >
>>> > Masoud Sharbiani
>>> >
>>> > (Tree used was cloned from:
>>> https://github.com/OGAWAHirofumi/linux-tux3.git
>>> > Branch used was: hirofumi-user)
>>>
>>> What error? Well, it might hit to version check. Can you try "hirofumi"
>>> branch for kernel? (master branch is old compared to tux3 mkfs,
>>> preparing to update now).
>>>
>>> Thanks.
>>> --
>>> OGAWA Hirofumi <hirofumi at mail.parknet.co.jp>
>>>
>>
>>
>> _______________________________________________
>> Tux3 mailing list
>> Tux3 at phunq.net
>> http://phunq.net/mailman/listinfo/tux3
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://phunq.net/pipermail/tux3/attachments/20150805/8ccccd0f/attachment.html>