headers
Tor Håkon Gjerde | 2 Mar 2003 18:45
Picon
Favicon

block size

How can i change the max block size in a way that makes it possible mount 
ntfs partitions with a block size of 64k ?

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 2 comments |
headers
Szakacsits Szabolcs | 2 Mar 2003 19:47
Picon

Re: block size


On Sun, 2 Mar 2003, Tor [ISO-8859-1] Hĺkon Gjerde wrote:

> How can i change the max block size in a way that makes it possible mount
> ntfs partitions with a block size of 64k ?

Mandrake 9.1 RC1 can mount it (2.4.21pre4-10mdk). It uses the new NTFS
driver (http://linux-ntfs.sf.net/downloads.html). I don't know if it
has any other additional patch to be able to do this. SuSE 8.0 using
the old NTFS driver couldn't (2.4.18-64GB-SMP).

	Szaka

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Anton Altaparmakov | 2 Mar 2003 19:58
Favicon

Re: block size

On Sun, 2 Mar 2003, Tor Håkon Gjerde wrote:
> How can i change the max block size in a way that makes it possible mount 
> ntfs partitions with a block size of 64k ?

You can't change the block size. However if you use the new ntfs driver
present in 2.5.x kernels and available as a patch to 2.4.20 kernel (also
part of the Mandrake Linux distro, possibly others, too) you will be able
to just mount the partition in question without any problems. The new
driver supports all blocksizes that Windows supports.

Best regards,

	Anton
--

-- 
Anton Altaparmakov <aia21 at cantab.net> (replace at with  <at> )
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
H. Peter Anvin | 4 Mar 2003 23:55
Favicon

Changing inode_operations

Hi all,

Does anyone know if there are any filesystems which change the
inode_operations on a directory after the directory inode has already
been instantiated?

I'm still hunting for a reasonable way to do autofs tree mounts
without atomicity problems...

	-hpa
--

-- 
<hpa <at> transmeta.com> at work, <hpa <at> zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Rajaram Suresh Gaunker | 5 Mar 2003 08:25
Favicon

which function writes to the disk

hi

which functions writes to the disk in file system?

how can i know which user wants to write to disk, or which user 
has called the system call?

user registers his key by using a system call which i'm 
providing
he can also unregister itself using a system call

the key for each user is stored in kernel when we are writing the 
data to file of user we will encrypt using owners key

plz comment on this

bye

R <at> j <at> r <at> m
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 2 comments |
headers
Heinz J . Mauelshagen | 5 Mar 2003 18:19
Picon
Favicon

www.sistina.com


Hi all,

A tarball is available at

   <http://www.sistina.com/>

for download.

Follow the "products" link on top of the Sistina web page
and then the "Logical Volume Manager" link.

LVM 1.0.7 fixes a persistent snapshot bug potentially causing
wrong snapshot content on resize.

See the CHANGELOG and WHATSNEW files contained in the tarball
for further information.

Feed back LVM related information to <linux-lvm <at> sistina.com>.

Thanks a lot for your support of LVM.

--

-- 

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jan Harkes | 5 Mar 2003 18:54
Picon
Favicon
Gravatar

Re: which function writes to the disk

On Wed, Mar 05, 2003 at 07:25:13AM -0000, Rajaram Suresh Gaunker wrote:
> which functions writes to the disk in file system?
> 
> how can i know which user wants to write to disk, or which user 
> has called the system call?

That is a little difficult, last time I looked, writes were just marking
the memory page dirty. At some point there is this kernel flush daemon
that wanders by, notices that the page is dirty and kicks off the actual
IO.

In the mean time several users might have written to the same page
before IO has even started which makes it unclear which user has
permission to write. Will all valid writes fail if one user's
permissions have expired? Or will we allow an user's writes to
succeed just because he is piggybacking on the valid writers.

> user registers his key by using a system call which i'm 
> providing he can also unregister itself using a system call
> 
> the key for each user is stored in kernel when we are writing the 
> data to file of user we will encrypt using owners key

You might want to google for 'cryptfs', 'cfs', and 'tcfs'.

Jan

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Chow | 6 Mar 2003 17:53

Re: Sick VFS question

Ion Badulescu wrote:

>On Tue, 25 Feb 2003, Charles P. Wright wrote:
>
>  
>
>>AFAIK, In FiST-lite what happens is the upper level (wrapfs) inode has its
>>address space operations set to the operations of the lower level (e.g.,
>>EXT2) inode.  A quick look at the code seemed to confirm this.
>>    
>>
>
>Hmm. You're probably right (you've been hacking that code more recently
>than I have...). Anyway, what I said initially was definitely the original
>approach for FiST-lite, and I guess my memory is getting fuzzy on recent
>details, even though I actively worked on them. :-)
>  
>
 From what I know about FiST, this is not quite true. The aops of wrapfs 
inode are not pointed to the lower level fs's aops. Most of the address 
space operations have a struct page, which a struct page have its 
mapping and host ref to inode. The lower level inode is ref by the 
wrapfs inode private data. The wrapgs has its own page cache and looks 
like a separate fs to the VFS in all aspects.

David

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
(Continue reading)

Permalink | Reply | 1 comment |
headers
Charles P. Wright | 6 Mar 2003 18:18

Re: Sick VFS question

On Fri, 7 Mar 2003, David Chow wrote:
> Ion Badulescu wrote:
> >On Tue, 25 Feb 2003, Charles P. Wright wrote:
> >>AFAIK, In FiST-lite what happens is the upper level (wrapfs) inode has its
> >>address space operations set to the operations of the lower level (e.g.,
> >>EXT2) inode.  A quick look at the code seemed to confirm this.
> >>    
> >>
> >
> >Hmm. You're probably right (you've been hacking that code more recently
> >than I have...). Anyway, what I said initially was definitely the original
> >approach for FiST-lite, and I guess my memory is getting fuzzy on recent
> >details, even though I actively worked on them. :-)
> >  
> >
>  From what I know about FiST, this is not quite true. The aops of wrapfs 
> inode are not pointed to the lower level fs's aops. Most of the address 
> space operations have a struct page, which a struct page have its 
> mapping and host ref to inode. The lower level inode is ref by the 
> wrapfs inode private data. The wrapgs has its own page cache and looks 
> like a separate fs to the VFS in all aspects.
David,

We've recently improved the FiST code, such that if you specify filter
data, this is indeed the case and a separate page cache is kept.  
However, if data is not filtered then FiST-lite is used (the method
described above).  This decreases performance overhead to about 1% over a
native file system (compared to full-blown FiST which is about 5%).

Charles
(Continue reading)

Permalink | Reply | 0 comments |
headers
anil vijarnia | 7 Mar 2003 06:24
Favicon

clean unmount?

hi everybody!

can anyone tell me how at bootup time the filesystem is checked 
for clean unmount,i mean which flags are set by umount() and 
checked at bootup time(paricularly the FAT filesystem).also which 
part of code checks this thing and calls 'fsck'
prog. if necessary.

regards
vijarnia

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |

Gmane