On Wed, Feb 27, 2008 at 6:17 AM, Bob Friesenhahn
<[EMAIL PROTECTED]> wrote:
> On Sun, 17 Feb 2008, Mertol Ozyoney wrote:
>
> > Hi Bob;
> >
> > When you have some spare time can you prepare a simple benchmark report in
> > PDF that I can share with my customers to demonstrate the performance of
It occurred to me that we are likely missing the point here because Uwe
is thinking of this as a One User on a System sort of perspective,
whereas most of the rest of us are thinking of it from a 'Solaris'
perspective, where we are typically expecting the system to be running
many applications
On Tue, Feb 26, 2008 at 06:34:04PM -0800, Uwe Dippel wrote:
> > The rub is this: how do you know when a file edit/modify has completed?
>
> Not to me, I'm sorry, this is task of the engineer, the implementer.
> (See 'atomic', as above.) It would be a shame if a file system never
> knew if the oper
On Wed, Feb 27, 2008 at 05:54:29AM +0200, Marcus Sundman wrote:
> Nathan Kroenert <[EMAIL PROTECTED]> wrote:
> > Are you indicating that the filesystem know's or should know what an
> > application is doing??
>
> Maybe "snapshot file whenever a write-filedescriptor is closed" or
> somesuch?
Agai
Uwe Dippel wrote:
>> atomic view?
>>
>
> Your post was on the gory details on how ZFS writes. "Atomic View" here is,
> that 'save' of a file is an 'atomic' operation: at one moment in time you
> click 'save', and some other moment in time it is done. It means indivisible,
> and from the per
Uwe Dippel <[EMAIL PROTECTED]> writes:
> Any completed write needs to be CDP-ed.
And that is the rub, precisely. There is nothing in the app <-> kernel
interface currently that indicates that a write has completed to a state
that is meaningful to the application.
__
On Sun, 17 Feb 2008, Mertol Ozyoney wrote:
> Hi Bob;
>
> When you have some spare time can you prepare a simple benchmark report in
> PDF that I can share with my customers to demonstrate the performance of
> 2540 ?
While I do not claim that it is "simple" I have created a report on my
configura
Nathan Kroenert <[EMAIL PROTECTED]> wrote:
> Are you indicating that the filesystem know's or should know what an
> application is doing??
Maybe "snapshot file whenever a write-filedescriptor is closed" or
somesuch?
- Marcus
___
zfs-discuss mailing li
[i]I think you're just looking for frequent backups, not necessarily capturing
every unique file version.[/i]
Thanks for your reply, Joe, but this is not my intention. I agree, that my
arguments here look like moving targets. They simply developed along the lines
of discussion. I'd still target
Are you indicating that the filesystem know's or should know what an
application is doing??
It seems to me that to achieve what you are suggesting, that's exactly
what it would take.
Or, you are assuming that there are no co-dependent files in
applications that are out there...
Whichever the
> atomic view?
Your post was on the gory details on how ZFS writes. "Atomic View" here is,
that 'save' of a file is an 'atomic' operation: at one moment in time you click
'save', and some other moment in time it is done. It means indivisible, and
from the perspective of the user this is how it
Are path-names text or raw data in zfs? I.e., is it possible to know
what the name of a file/dir/whatever is, or do I have to make more or
less wild guesses what encoding is used where?
- Marcus
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
ht
> Can someone please point me to link, or just
> unambiguously say 'yes' or 'no' to my question, if
> ZFS could produce a snapshot of whatever type,
> initiated with a signal that in turn is derived from
> a change (edit) of a file; like inotify in Linux
> 2.6.13 and above.
Hi Uwe,
As I understan
Can someone please point me to link, or just unambiguously say 'yes'
or 'no' to my question, if ZFS could produce a snapshot of whatever
type, initiated with a signal that in turn is derived from a change
(edit) of a file; like inotify in Linux 2.6.13 and above.
Hi Uwe,
I wasn't previously fa
On Wed, Feb 27, 2008 at 01:45:41AM +0800, Uwe Dippel wrote:
> Sorry, I don't understand any of this. But I never pretended I did.
Well, if you want some feature then you should understand what it is.
Sure "continuous data protection" sounds real good, but you have to
understand that any CDP soluti
On Tue, Feb 26, 2008 at 2:07 PM, Nicolas Williams
<[EMAIL PROTECTED]> wrote:
> How do you use CDP "backups"? How do you decide at which write(2) (or
> dirty page write, or fsync(2), ...) to restore some file? What if the
> app has many files? Point-in-time? Sure, but since you can't restore
>
Rich Teer <[EMAIL PROTECTED]> wrote:
> > Are you interested only in full backups and in the ability to restore
> > single
> > files from that type of backups?
> >
> > Or are you interested in incremental backups that _also_ allow you to
> > reduce the
> > daily backup size but still gives you
On Feb 26, 2008, at 10:23 AM, Rich Teer wrote:
> On Tue, 26 Feb 2008, Joerg Schilling wrote:
>
>> Hi Rich, I asked you a question that you did not yet answer:
>
> Hi Jörg,
>
>> Are you interested only in full backups and in the ability to
>> restore single
>> files from that type of backups?
>>
On Tue, 26 Feb 2008, Joerg Schilling wrote:
> Hi Rich, I asked you a question that you did not yet answer:
Hi Jörg,
> Are you interested only in full backups and in the ability to restore single
> files from that type of backups?
>
> Or are you interested in incremental backups that _also_ all
Actually, i have some corrections to be made. When i did see the numbers, i was
stunned and that blocked me to think…
Here you can see the right numbers: http://www.posix.brte.com.br/blog/?p=104
The problem was the discs were i have made the tests.
Thanks for your time.
This message posted fr
Hey
Thanks for your answers guys.
I'll run VTS to stresstest cpu and memory.
And I just checked the block diagram of my motherboard (Gigabyte M61P-S3).
It doesn't even have 64bit pci slots.. just standard old 33mhz 32bit pci .. and
a couple of newer pci-e.
But my two controllers are both the sa
I would imagine that linux to behave more like ZFS that does not flush
caches.
(google Evil zfs_nocacheflush).
If you can nfs tar extract files on linux faster than one file per
rotation latency;
that is suspicious.
-r
Le 26 févr. 08 à 13:16, msl a écrit :
>> For Linux NFS service, it's a
Hi All,
I have modified zdb to do decompression in zdb_read_block. Syntax is:
# zdb -R poolname:devid:blkno:psize:d,compression_type,lsize
Where compression_type can be lzjb or any other type compression that
zdb uses, and
lsize is the size after compression. I have used this with a modified
> For Linux NFS service, it's a option in
> /etc/exports.
>
> The default for "modern" (post-1.0.1) NFS utilities
> is "sync", which means that data and metadata will be
> written to the disk whenever NFS requires it
> (generally upon an NFS COMMIT operation). This is
> the same as Solaris with U
Darren J Moffat <[EMAIL PROTECTED]> wrote:
> ZFS discuss is fine but the thread has gone into non ZFS related and is
> generic backup stuff. If there are ZFS specifics - like the question
> about extended attributes then I think this is a reasonable place to
> discuss. Discussion about nomenc
michael schuster <[EMAIL PROTECTED]> wrote:
> Rich never said so. He said "the ability to do incremental backups and
> restore arbitrary files from an archive are two different things." You were
> addressing an issue he never brought up.
I really don't understand why you did not answer my quest
Rich Teer <[EMAIL PROTECTED]> wrote:
> > People who like to backup usually also like to do incremental backups.
> > Why don't you?
>
> I do like incremental backups. But the ability to do incremental backups
> and restore arbitrary files from an archive are two different things. An
> incremental
Le lundi 25 février 2008 à 11:05 -0800, Sandro a écrit :
> hi folks
Hi,
> I've been running my fileserver at home with linux for a couple of years and
> last week I finally reinstalled it with solaris 10 u4.
>
> I borrowed a bunch of disks from a friend, copied over all the files,
> reinstalle
28 matches
Mail list logo
