similar to: ZFS vs UFS2 overhead and may be a bug?

Hello, I'm running centos5 with the centosplus kernel v2.6.18-8.1.8.el5 and i'm trying to read a drive that has a ufs2 partition on it. It was originally in a FreeBSD machine and has some data i'd like to get at. Googling indicated this should work with the command: mount -r -t ufs -o ufstype=ufs2 <device> <mountpoint> device is /dev/hdb5 and mountpoint is /mnt.

Hi, This is my first post to this list. I have been backing up some files with rsync from My Mac OS X 10.4.7 machine, which uses HFS+ filesystem to a FreeBSD 6.1-RELEASE machine, which uses UFS2 filesystem. They go across a 100-base-T lan, which has little or no traffic on it. On my Mac, I mount the nfs exported volume on the FreeBSD machine with: $ mount -t nfs moe:/backup

Hello openssh@ I thought about sftp's reget/reput commands. Several days ago, Damien Miller write to tech at openbsd.org (it was reply for my letter): > Herein lies a problem which is not easy to detect or solve. For > performance reasons, the sftp client does pipelined reads/writes when > transferring files. The protocol spec allows for a server to process > these requests out

Hi Genec, On Sun, May 25, 2014 11:27 am, Gene Cumm wrote: > Raphael/Paulo: does UFS2 have a hard 64kiB limit? I know it's not > installed to the first sector where the first superblock is located. I have no much experience with UFS2 filesystem. I've just took a quick look at its internals and I can see that UFS2 places its superblock at either 64KiB or 256KiB (depending on the

It's needed to enumerate both UFS1/2 since they have different magic numbers and super block offsets. Besides, UFS2 can be installed in the 0-64k range like BTRFS, whereas UFS1 can't. UFS2 has no cow feature unlike BTRFS. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- extlinux/main.c | 79 ++++++++++--- extlinux/ufs.h | 26 ++++

On Fri, 12 Jul, at 08:31:27PM, Raphael S.Carvalho wrote: > @@ -575,7 +594,7 @@ bail: > return 1; > } > > -/* btrfs has to install the ldlinux.sys in the first 64K blank area, which > +/* btrfs/ufs2 has to install the ldlinux.sys in the first 64K blank area, which > is not managered by btrfs tree, so actually this is not installed as files. > since the cow

It's needed to enumerate both UFS1/2 since they have different magic numbers and super block offsets. Besides, UFS2 can be installed in the 0-64k range like BTRFS, whereas UFS1 can't. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- extlinux/main.c | 71 +++++++++--- extlinux/ufs.h | 26 ++++ extlinux/ufs_fs.h | 307

On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote: > > > While going throug old posts found: > > Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho: > > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. > > ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. >

> On Apr 23, 2018, at 10:49 AM, WK <wkmail at bneit.com> wrote: > > From some old May 2017 email. I asked the following: > "From the docs, I see you can identify the shards by the GFID > # getfattr -d -m. -e hex path_to_file > # ls /bricks/*/.shard -lh | grep GFID > > Is there a gluster tool/script that will recreate the file? > > or can you just sort

From: Raphael S. Carvalho <raphael.scarv at gmail.com> It's already loading modules successfully, booting Linux, and both UFS version 1 and 2 seem to be working correctly. Signed-off-by: Raphael S. Carvalho <raphael.scarv at gmail.com> --- core/fs/ufs/bmap.c | 202 ++++++++++++++++++++++++++ core/fs/ufs/ufs.c | 404 ++++++++++++++++++++++++++++++++++++++++++++++++++++

It's already loading modules successfully, and both UFS version 1 and 2 seems to be working correctly. Special thanks to Paulo Alcantara and Matt Fleming for being always ready to help me and give feedback. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- core/fs/ufs/bmap.c | 202 ++++++++++++++++++++++++++ core/fs/ufs/ufs.c | 404

> On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote: > > > > > > While going throug old posts found: > > > > Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho: > > > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds > the limit. > > > ldlinux.sys must fit between the bootsector and

There is a confusion about the name of this file system, then I decided to contact the author (Kirk McKusick) who replied: "The name has always been confusing (my bad). The code is broken into two parts, the part that handles naming (UFS where the U stands for Unix), and the part that handles disk layout (FFS where the F stands for Fast). When the two parts are put together they are called

hello, people! could you advice me some kind of computer audio recording programme to write music 'on-the-fly' from line-in sound card exit to ogg vorbis file directly. for example, there is an 'absolute mp3 recorder', but i would like to record audio in ogg vorbis. -- kind regards, maxim abalenkov http://maniac.times.lv copy writer mail to: vault13@inbox.lv

Hi all, I am playing with a test box at the moment running a Samba 2.2.7a domain on FreeBSD 5.0. I wish to enable ACLs, but I am not exactly sure what I am supposed to expect once they are enabled. I have created a UFS2 partition and enabled ACL support using tunefs. Since doing that, I have been able to connect to the Samba shares and modify ACLs, but so far the only things I have been able to

Hello everyone, Stopped by Best Buy last night and picked up a Rio Karma. Since from-the-trenches reviews seem scarce, I thought I might post some thoughts. The short story: I'm probably returning it, will be buying a different portable player. The software doesn't work, and I don't think I wanna screw with it. The long story: It looks cool, is tiny,

From: Raphael S. Carvalho <raphael.scarv at gmail.com> v2: Extract ADV_SIZE automatically from libinstaller/setadv.h. Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys can be at most: 65536 - 2 * ADV_SIZE - 512 (limit). Certain file systems

On Sun, May 25, 2014 at 10:27 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > Raphael/Paulo: does UFS2 have a hard 64kiB limit? I know it's not installed > to the first sector where the first superblock is located. Momentarily confused UFS2 and the madness of XFS putting its superblock into sector 0, rendering it unusable for typical boot purposes. -- -Gene

Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range, thus it can't exceed the limit,

Peter, does this look OK to you? Raphael, I can't work out why ADV_SIZE is a constant in this file? On Sat, 31 Aug, at 05:01:20PM, Raphael S.Carvalho wrote: > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. > ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. > Thus, the size of ldlinux.sys (limit) can be at most: